Transform block size restriction in video coding

ABSTRACT

A visual media processing method includes performing a conversion between a current video block of a visual media data and a bitstream representation of the current video block, wherein the bitstream representation is configured according to a format rule that specifies that a syntax element is selectively included or excluded in the bitstream representation indicative of a maximum number of merge candidates for a coding tool, thereby indicating whether the coding tool is enabled or disabled for the conversion, wherein the maximum number of merge candidates for the coding tool is zero or a positive number.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent Application No. PCT/CN2020/101819, filed on Jul. 14, 2020, which claims the priority to and benefits of International Patent Application No. PCT/CN2019/095921, filed on Jul. 14, 2019. All the aforementioned patent applications are hereby incorporated by reference in their entireties.

TECHNICAL FIELD

This document is related to video and image coding and decoding technologies.

BACKGROUND

Digital video accounts for the largest bandwidth use on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, it is expected that the bandwidth demand for digital video usage will continue to grow.

SUMMARY

In one example aspect, a method of visual media processing is disclosed. The method includes performing a conversion between a current video block of a visual media data and a bitstream representation of the current video block, wherein the bitstream representation is configured according to a format rule that specifies that a syntax element is selectively included or excluded in the bitstream representation indicative of a maximum number of merge candidates for a coding tool, thereby indicating whether the coding tool is enabled or disabled for the conversion, wherein the maximum number of merge candidates for the coding tool is zero or a positive number.

In one example aspect, a method of visual media processing is disclosed. The method includes performing a conversion between a video comprising one or more video regions comprising multiple video blocks and a bitstream representation of the video, wherein the bitstream representation conforms to a format rule specifying that a number of allowed geometric partitioning mode (GPM) motion candidates for a video region determines whether a syntax element related to applicability of a coding tool to the video region is included in the bitstream representation, wherein the coding tool is different from a GPM coding tool, wherein the GPM comprises splitting a video block into multiple prediction partitions to apply motion prediction separately, and at least one partition having a non-rectangular shape.

In one example aspect, a method of visual media processing is disclosed. The method includes performing a conversion between a current video unit of a visual media data and a bitstream representation of the visual media data, wherein the bitstream representation is configured in accordance with a format rule that specifies that a maximum transform block size is equal to or less than a maximum coding tree unit (CTU) size used for the conversion.

In one example aspect, a method of visual media processing is disclosed. The method includes performing a conversion between a current video block of a visual media data and a bitstream representation of the current video block, wherein the conversion uses an adaptive loop filter (ALF) in which coefficients of the ALF filter are based on a depth of a sample in a video region of the current video block.

In one example aspect, a method of visual media processing is disclosed. The method includes performing a conversion between a current video block of a visual media data and a bitstream representation of the current video block using an adaptive loop filter (ALF), wherein the bitstream representation is configured according to a format rule specifying that one or more syntax elements included in the bitstream representation indicative of whether an ALF filter applied to the current video block is determined based on an adaptation parameter set (APS) or based on fixed filter sets.

In another example aspect, the above-described methods may be implemented by a video decoder apparatus that comprises a processor.

In another example aspect, the above-described methods may be implemented by a video encoder apparatus that comprises a processor.

In yet another example aspect, these methods may be embodied in the form of processor-executable instructions and stored on a computer-readable program medium.

These, and other, aspects are further described in the present document.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a derivation process for merge candidate list construction.

FIG. 2 shows an example of positions of spatial merge candidates.

FIG. 3 shows an example of candidate pairs considered for redundancy check of spatial merge candidates.

FIG. 4 shows an example positions for the second PU of N×2N and 2N×N partitions.

FIG. 5 shows examples of illustration of motion vector scaling for temporal merge candidate.

FIG. 6 shows an example of candidate positions for temporal merge candidate, C0 and C1.

FIG. 7 shows example of combined bi-predictive merge candidate.

FIG. 8 shows examples of derivation process for motion vector prediction candidates.

FIG. 9 shows an example illustration of motion vector scaling for spatial motion vector candidate.

FIG. 10 shows an example simplified affine motion model for 4-parameter affine mode (left) and 6-parameter affine model (right).

FIG. 11 shows an example of affine motion vector field per sub-block.

FIG. 12 shows an example Candidates position for affine merge mode.

FIG. 13 shows an example of Modified merge list construction process.

FIG. 14 shows an example of triangle partition based inter prediction.

FIG. 15 shows an example of a CU applying the 1^(st) weighting factor group.

FIG. 16 shows an example of motion vector storage.

FIG. 17 shows an example of ultimate motion vector expression (UMVE) search process.

FIG. 18 shows an example of UMVE search points.

FIG. 19 shows an example of MVD (0, 1) mirrored between list 0 and list 1 in DMVR.

FIG. 20 shows MVs that may be checked in one iteration.

FIG. 21 is an example of intra block copy.

FIG. 22 is a block diagram of an example of a video processing apparatus.

FIG. 23 is a flowchart for an example of a video processing method.

FIG. 24 is a block diagram of an example video processing system in which disclosed techniques may be implemented.

FIG. 25 is a flowchart for an example of a visual media processing method.

FIG. 26 is a flowchart for an example of a visual media processing method.

FIG. 27 is a flowchart for an example of a visual media processing method.

FIG. 28 is a flowchart for an example of a visual media processing method.

FIG. 29 is a flowchart for an example of a visual media processing method.

DETAILED DESCRIPTION

The present document provides various techniques that can be used by a decoder of image or video bitstreams to improve the quality of decompressed or decoded digital video or images. For brevity, the term “video” is used herein to include both a sequence of pictures (traditionally called video) and individual images. Furthermore, a video encoder may also implement these techniques during the process of encoding in order to reconstruct decoded frames used for further encoding.

Section headings are used in the present document for ease of understanding and do not limit the embodiments and techniques to the corresponding sections. As such, embodiments from one section can be combined with embodiments from other sections.

1. Brief Summary

This document is related to video coding technologies. Specifically, it is related to merge coding including triangular prediction mode. It may be applied to the existing video coding standard like HEVC, or the standard (Versatile Video Coding) to be finalized. It may be also applicable to future video coding standards or video codec.

2. Initial Discussion

Video coding standards have evolved primarily through the development of the well-known ITU-T and ISO/IEC standards. The ITU-T produced H.261 and H.263, ISO/IEC produced MPEG-1 and MPEG-4 Visual, and the two organizations jointly produced the H. 262/MPEG-2 Video and H. 264/MPEG-4 Advanced Video Coding (AVC) and H.265/HEVC standards. Since H.262, the video coding standards are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized. To explore the future video coding technologies beyond HEVC, Joint Video Exploration Team (JVET) was founded by VCEG and MPEG jointly in 2015. Since then, many new methods have been adopted by JVET and put into the reference software named Joint Exploration Model (JEM). In April 2018, the Joint Video Expert Team (JVET) between VCEG (Q6/16) and ISO/IEC JTC1 SC29/WG11 (MPEG) was created to work on the VVC standard targeting at 50% bitrate reduction compared to HEVC.

The latest version of VVC draft, i.e., Versatile Video Coding (Draft 5) could be found at: http://phenix.it-sudparis.eu/jvet/doc_end_user/documents/14_Geneva/wg11/JVET-N1001-v7.zip

The latest reference software of VVC, named VTM, could be found at: https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/tags/VTM-5.0

2.1 Inter Prediction in HEVC/H.265

For inter-coded coding units (CUs), it may be coded with one prediction unit (PU), 2 PUs according to partition mode. Each inter-predicted PU has motion parameters for one or two reference picture lists. Motion parameters include a motion vector and a reference picture index. Usage of one of the two reference picture lists may also be signalled using inter_pred_idc. Motion vectors may be explicitly coded as deltas relative to predictors.

When a CU is coded with skip mode, one PU is associated with the CU, and there are no significant residual coefficients, no coded motion vector delta or reference picture index. A merge mode is specified whereby the motion parameters for the current PU are obtained from neighbouring PUs, including spatial and temporal candidates. The merge mode can be applied to any inter-predicted PU, not only for skip mode. The alternative to merge mode is the explicit transmission of motion parameters, where motion vector (to be more precise, motion vector differences (MVD) compared to a motion vector predictor), corresponding reference picture index for each reference picture list and reference picture list usage are signalled explicitly per each PU. Such a mode is named Advanced motion vector prediction (AMVP) in this disclosure.

When signalling indicates that one of the two reference picture lists is to be used, the PU is produced from one block of samples. This is referred to as ‘uni-prediction’. Uni-prediction is available both for P-slices and B-slices.

When signalling indicates that both of the reference picture lists are to be used, the PU is produced from two blocks of samples. This is referred to as ‘bi-prediction’. Bi-prediction is available for B-slices only.

The following text provides the details on the inter prediction modes specified in HEVC. The description will start with the merge mode.

2.1.1 Reference Picture List

In HEVC, the term inter prediction is used to denote prediction derived from data elements (e.g., sample values or motion vectors) of reference pictures other than the current decoded picture. Like in H. 264/AVC, a picture can be predicted from multiple reference pictures. The reference pictures that are used for inter prediction are organized in one or more reference picture lists. The reference index identifies which of the reference pictures in the list should be used for creating the prediction signal.

A single reference picture list, List 0, is used for a P slice and two reference picture lists, List 0 and List 1 are used for B slices. It should be noted reference pictures included in List 0/1 could be from past and future pictures in terms of capturing/display order.

2.1.2 Merge Mode 2.1.2.1 Derivation of Candidates for Merge Mode

When a PU is predicted using merge mode, an index pointing to an entry in the merge candidates list is parsed from the bitstream and used to retrieve the motion information. The construction of this list is specified in the HEVC standard and can be summarized according to the following sequence of steps:

-   -   Step 1: Initial candidates derivation         -   Step 1.1: Spatial candidates derivation         -   Step 1.2: Redundancy check for spatial candidates         -   Step 1.3: Temporal candidates derivation     -   Step 2: Additional candidates insertion         -   Step 2.1: Creation of bi-predictive candidates         -   Step 2.2: Insertion of zero motion candidates

These steps are also schematically depicted in FIG. 1. For spatial merge candidate derivation, a maximum of four merge candidates are selected among candidates that are located in five different positions. For temporal merge candidate derivation, a maximum of one merge candidate is selected among two candidates. Since constant number of candidates for each PU is assumed at decoder, additional candidates are generated when the number of candidates obtained from step 1 does not reach the maximum number of merge candidate (MaxNumMergeCand) which is signalled in slice header. Since the number of candidates is constant, index of best merge candidate is encoded using truncated unary binarization (TU). If the size of CU is equal to 8, all the PUs of the current CU share a single merge candidate list, which is identical to the merge candidate list of the 2N×2N prediction unit.

In the following, the operations associated with the aforementioned steps are detailed.

2.1.2.2 Spatial Candidates Derivation

In the derivation of spatial merge candidates, a maximum of four merge candidates are selected among candidates located in the positions depicted in FIG. 2. The order of derivation is A₁, B₁, B₀, A₀ and B₂. Position B₂ is considered only when any PU of position A₁, B₁, B₀, A₀ is not available (e.g. because it belongs to another slice or tile) or is intra coded. After candidate at position A₁ is added, the addition of the remaining candidates is subject to a redundancy check which ensures that candidates with same motion information are excluded from the list so that coding efficiency is improved. To reduce computational complexity, not all possible candidate pairs are considered in the mentioned redundancy check. Instead only the pairs linked with an arrow in FIG. 3 are considered and a candidate is only added to the list if the corresponding candidate used for redundancy check has not the same motion information. Another source of duplicate motion information is the “second PU” associated with partitions different from 2N×2N. As an example, FIG. 4 depicts the second PU for the case of N×2N and 2N×N, respectively. When the current PU is partitioned as N×2N, candidate at position A₁ is not considered for list construction. In fact, by adding this candidate will lead to two prediction units having the same motion information, which is redundant to just have one PU in a coding unit. Similarly, position B₁ is not considered when the current PU is partitioned as 2N×N.

2.1.2.3 Temporal Candidates Derivation

In this step, only one candidate is added to the list. Particularly, in the derivation of this temporal merge candidate, a scaled motion vector is derived based on co-located PU in a co-located picture. The scaled motion vector for temporal merge candidate is obtained as illustrated by the dotted line in FIG. 5, which is scaled from the motion vector of the co-located PU using the POC distances, tb and td, where tb is defined to be the POC difference between the reference picture of the current picture and the current picture and td is defined to be the POC difference between the reference picture of the co-located picture and the co-located picture. The reference picture index of temporal merge candidate is set equal to zero. A practical realization of the scaling process is described in the HEVC specification [1]. For a B-slice, two motion vectors, one is for reference picture list 0 and the other is for reference picture list 1, are obtained and combined to make the bi-predictive merge candidate.

2.1.2.4 Co-Located Picture and Co-Located PU

When TMVP is enabled (i.e., slice_temporal_mvp_enabled_flag is equal to 1), the variable ColPic representing the col-located picture is derived as follows:

-   If current slice is B slice and the signalled     collocated_from_l0_flag is equal to 0, ColPic is set equal to     RefPicList1[collocated_ref_idx]. -   Otherwise (slice_type is equal to B and collocated_from_l0_flag is     equal to 1, or slice_type is equal to P), ColPic is set equal to     RefPicList0[collocated_ref_idx].     wherein collocated_ref_idx and collocated_from_l0_flag are two     syntax elements which may be signalled in slice header.

In the co-located PU (Y) belonging to the reference frame, the position for the temporal candidate is selected between candidates C₀ and C₁, as depicted in FIG. 6. If PU at position C₀ is not available, is intra coded, or is outside of the current coding tree unit (CTU aka. LCU, largest coding unit) row, position C₁ is used. Otherwise, position C₀ is used in the derivation of the temporal merge candidate.

Related syntax elements are described as follows:

7.3.6.1 General Slice Segment Header Syntax

Descriptor slice_segment_header( ) {  first_slice_segment_in_pic_flag u(1) . . .   if( slice_type == P || slice_type == B) {    num_ref_idx_active_override_flag u(1)    if( num_ref_idx_active_override_flag) {     num_ref_idx_l0_active_minus1 ue(v)     if( slice_type == B)      num_ref_idx_l1_active_minus1 ue(v)    } . . .    IF( SLICE_TEMPORAL_MVP_ENABLED_FLAG) {     IF( SLICE_TYPE == B)     COLLOCATED_FROM_L0_FLAG U(1)     IF( (COLLOCATED_FROM_L0_FLAG && NUM_REF_IDX_L0_ACTIVE_MINUS1>0) ||     (!COLLOCATED_FROM_L0_FLAG && NUM_REF_IDX_L1_ACTIVE_MINUS1>0))     COLLOCATED_REF_IDX UE(V)    } . . .  byte_alignment( ) }

2.1.2.5 Derivation of MVs for the TMVP Candidate

More specifically, the following steps are performed in order to derive the TMVP candidate:

-   1) set reference picture list X=0, target reference picture to be     the reference picture with index equal to 0 (i.e., curr_ref) in     list X. Invoke the derivation process for collocated motion vectors     to get the MV for list X pointing to curr_ref. -   2) if current slice is B slice, set reference picture list X=1,     target reference picture to be the reference picture with index     equal to 0 (i.e., curr_ref) in list X. Invoke the derivation process     for collocated motion vectors to get the MV for list X pointing to     curr_ref.

The derivation process for collocated motion vectors is described in the next sub-section 2.1.2.5.1.

2.1.2.5.1 Derivation Process for Collocated Motion Vectors

For the co-located block, it may be intra or inter coded with uni-prediction or bi-prediction. If it is intra coded, TMVP candidate is set to be unavailable.

If it is uni-prediction from list A, the motion vector of list A is scaled to the target reference picture list X.

If it is bi-prediction and the target reference picture list is X, the motion vector of list A is scaled to the target reference picture list X, and A is determined according to the following rules:

-   -   If none of reference pictures has a greater POC values compared         to current picture, A is set equal to X.     -   Otherwise, A is set equal to collocated_from_l0_flag.

The related working draft in JCTVC-W1005-v4 is described as follows:

8.5.3.2.9 Derivation Process for Collocated Motion Vectors

Inputs to this process are:

-   a variable currPb specifying the current prediction block, -   a variable colPb specifying the collocated prediction block inside     the collocated picture specified by ColPic, -   a luma location (xColPb, yColPb) specifying the top-left sample of     the collocated luma prediction block specified by colPb relative to     the top-left luma sample of the collocated picture specified by     ColPic, -   a reference index refIdxLX, with X being 0 or 1.

Outputs of this process are:

-   the motion vector prediction mvLXCol, -   the availability flag availableFlagLXCol.

The variable currPic specifies the current picture.

The arrays predFlagL0Col[x][y], mvL0Col[x][y], and refIdxL0Col[x][y] are set equal to PredFlagL0[x][y], MvL0[x][y], and RefIdxL0[x][y], respectively, of the collocated picture specified by ColPic, and the arrays predFlagL1Col[x][y], myL1Col[x][y], and refIdxL1Col[x][y] are set equal to PredFlagL1[x][y], MvL1[x][y], and RefIdxL1[x][y], respectively, of the collocated picture specified by ColPic.

The variables mvLXCol and availableFlagLXCol are derived as follows:

-   If colPb is coded in an intra prediction mode, both components of     mvLXCol are set equal to 0 and availableFlagLXCol is set equal to 0. -   Otherwise, the motion vector mvCol, the reference index refIdxCol,     and the reference list identifier listCol are derived as follows:     -   If predFlagL0Col[xColPb][yColPb] is equal to 0, mvCol,         refIdxCol, and listCol are set equal to mvL1Col[xColPb][yColPb],         refIdxL1Col[xColPb][yColPb], and L1, respectively.     -   Otherwise, if predFlagL0Col[xColPb][yColPb] is equal to 1 and         predFlagL1Col[xColPb][yColPb] is equal to 0, mvCol, refIdxCol,         and listCol are set equal to myL0Col[xColPb][yColPb],         refIdxL0Col[xColPb][yColPb], and L0, respectively.     -   Otherwise (predFlagL0Col[xColPb][yColPb] is equal to 1 and         predFlagL1Col[xColPb][yColPb] is equal to 1), the following         assignments are made:         -   If NoBackwardPredFlag is equal to 1, mvCol, refIdxCol, and             listCol are set equal to mvLXCol[xColPb][yColPb],             refIdxLXCol[xColPb][yColPb], and LX, respectively.         -   Otherwise, mvCol, refIdxCol, and listCol are set equal to             mvLNCol[xColPb][yColPb], refIdxLNCol[xColPb][yColPb], and             LN, respectively, with N being the value of             collocated_from_l0_flag.             and mvLXCol and availableFlagLXCol are derived as follows:     -   If LongTermRefPic(currPic, currPb, refIdxLX, LX) is not equal to         LongTermRefPic(ColPic, colPb, refIdxCol, listCol), both         components of mvLXCol are set equal to 0 and availableFlagLXCol         is set equal to 0.     -   Otherwise, the variable availableFlagLXCol is set equal to 1,         refPicListCol[refIdxCol] is set to be the picture with reference         index refIdxCol in the reference picture list listCol of the         slice containing prediction block colPb in the collocated         picture specified by ColPic, and the following applies:

colPocDiff=DiffPicOrderCnt(ColPic, refPicListCol[refIdxCol])  (2-1)

currPocDiff=DiffPicOrderCnt(currPic, RefPicListX[refIdxLX])  (2-2)

-   -   If RefPicListX[refIdxLX] is a long-term reference picture, or         colPocDiff is equal to currPocDiff, mvLXCol is derived as         follows:

mvLXCol=mvCol  (2-3)

-   -   Otherwise, mvLXCol is derived as a scaled version of the motion         vector mvCol as follows:

tx=(16384+(Abs(td)>>1))/td  (2-4)

distScaleFactor=Clip3(−4096, 4095,(tb*tx+32)>>6)  (2-5)

mvLXCol=Clip3(−32768, 32767, Sign(distScaleFactor*mvCol)*((Abs(distScaleFactor*mvCol)+127)>>8))  (2-6)

-   -    where td and tb are derived as follows:

td=Clip3(−128, 127, colPocDiff)  (2-7)

td=Clip3(−128, 127, currPocDiff)  (2-8)

Definition of NoBackwardPredFlag is:

The variable NoBackwardPredFlag is derived as follows:

-   If DiffPicOrderCnt(aPic, CurrPic) is less than or equal to 0 for     each picture aPic in RefPicListO or RefPicList1 of the current     slice, NoBackwardPredFlag is set equal to 1. -   Otherwise, NoBackwardPredFlag is set equal to 0.

2.1.2.6 Additional Candidates Insertion

Besides spatial and temporal merge candidates, there are two additional types of merge candidates: combined bi-predictive merge candidate and zero merge candidate. Combined bi-predictive merge candidates are generated by utilizing spatial and temporal merge candidates. Combined bi-predictive merge candidate is used for B-Slice only. The combined bi-predictive candidates are generated by combining the first reference picture list motion parameters of an initial candidate with the second reference picture list motion parameters of another. If these two tuples provide different motion hypotheses, they will form a new bi-predictive candidate. As an example, FIG. 7 depicts the case when two candidates in the original list (on the left), which have mvL0 and refIdxL0 or mvL1 and refIdxL1, are used to create a combined bi-predictive merge candidate added to the final list (on the right). There are numerous rules regarding the combinations which are considered to generate these additional merge candidates, defined in [1].

Zero motion candidates are inserted to fill the remaining entries in the merge candidates list and therefore hit the MaxNumMergeCand capacity. These candidates have zero spatial displacement and a reference picture index which starts from zero and increases every time a new zero motion candidate is added to the list. Finally, no redundancy check is performed on these candidates.

2.1.3 AMVP

AMVP exploits spatio-temporal correlation of motion vector with neighbouring PUs, which is used for explicit transmission of motion parameters. For each reference picture list, a motion vector candidate list is constructed by firstly checking availability of left, above temporally neighbouring PU positions, removing redundant candidates and adding zero vector to make the candidate list to be constant length. Then, the encoder can select the best predictor from the candidate list and transmit the corresponding index indicating the chosen candidate. Similarly with merge index signalling, the index of the best motion vector candidate is encoded using truncated unary. The maximum value to be encoded in this case is 2 (see FIG. 8). In the following sections, details about derivation process of motion vector prediction candidate are provided.

2.1.3.1 Derivation of AMVP Candidates

FIG. 8 summarizes derivation process for motion vector prediction candidate.

In motion vector prediction, two types of motion vector candidates are considered: spatial motion vector candidate and temporal motion vector candidate. For spatial motion vector candidate derivation, two motion vector candidates are eventually derived based on motion vectors of each PU located in five different positions as depicted in FIG. 2.

For temporal motion vector candidate derivation, one motion vector candidate is selected from two candidates, which are derived based on two different co-located positions. After the first list of spatio-temporal candidates is made, duplicated motion vector candidates in the list are removed. If the number of potential candidates is larger than two, motion vector candidates whose reference picture index within the associated reference picture list is larger than 1 are removed from the list. If the number of spatio-temporal motion vector candidates is smaller than two, additional zero motion vector candidates is added to the list.

2.1.3.2 Spatial Motion Vector Candidates

In the derivation of spatial motion vector candidates, a maximum of two candidates are considered among five potential candidates, which are derived from PUs located in positions as depicted in FIG. 2, those positions being the same as those of motion merge. The order of derivation for the left side of the current PU is defined as A₀, A₁, and scaled A₀, scaled A₁. The order of derivation for the above side of the current PU is defined as B₀, B₁, B₂, scaled B₀, scaled B₁, scaled B₂. For each side there are therefore four cases that can be used as motion vector candidate, with two cases not required to use spatial scaling, and two cases where spatial scaling is used. The four different cases are summarized as follows.

-   -   No Spatial Scaling         -   (1) Same reference picture list, and same reference picture             index (same POC)         -   (2) Different reference picture list, but same reference             picture (same POC)     -   Spatial Scaling         -   (3) Same reference picture list, but different reference             picture (different POC)         -   (4) Different reference picture list, and different             reference picture (different POC)

The no-spatial-scaling cases are checked first followed by the spatial scaling. Spatial scaling is considered when the POC is different between the reference picture of the neighbouring PU and that of the current PU regardless of reference picture list. If all PUs of left candidates are not available or are intra coded, scaling for the above motion vector is allowed to help parallel derivation of left and above MV candidates. Otherwise, spatial scaling is not allowed for the above motion vector.

In a spatial scaling process, the motion vector of the neighbouring PU is scaled in a similar manner as for temporal scaling, as depicted as FIG. 9. The main difference is that the reference picture list and index of current PU is given as input; the actual scaling process is the same as that of temporal scaling.

2.1.3.3 Temporal Motion Vector Candidates

Apart for the reference picture index derivation, all processes for the derivation of temporal merge candidates are the same as for the derivation of spatial motion vector candidates (see FIG. 6). The reference picture index is signalled to the decoder.

2.2 Inter Prediction Methods in VVC

There are several new coding tools for inter prediction improvement, such as Adaptive Motion Vector difference Resolution (AMVR) for signaling MVD, Merge with Motion Vector Differences (MMVD), Triangular prediction mode (TPM), Combined intra-inter prediction (CIIP), Advanced TMVP (ATMVP, aka SbTMVP), affine prediction mode, Generalized Bi-Prediction (GBI), Decoder-side Motion Vector Refinement (DMVR) and Bi-directional Optical flow (BIO, a. k. a BDOF).

There are three different merge list construction processes supported in VVC:

-   -   1) Sub-block merge candidate list: it includes ATMVP and affine         merge candidates. One merge list construction process is shared         for both affine modes and ATMVP mode. Here, the ATMVP and affine         merge candidates may be added in order. Sub-block merge list         size is signaled in slice header, and maximum value is 5.     -   2) Regular merge list: For inter-coded blocks, one merge list         construction process is shared. Here, the spatial/temporal merge         candidates, HMVP, pairwise merge candidates and zero motion         candidates may be inserted in order. Regular merge list size is         signaled in slice header, and maximum value is 6. MMVD, TPM,         CIIP rely on the regular merge list.     -   3) IBC merge list: it is done in a similar way as the regular         merge list.

Similarly, there are three AMVP lists supported in VVC:

-   -   1) Affine AMVP candidate list     -   2) Regular AMVP candidate list     -   3) IBC AMVP candidate list: the same construction process as the         IBC merge list due to the adoption of JVET-N0843

2.2.1 Coding Block Structure in VVC

In VVC, a Quad-Tree/Binary Tree/Ternary-Tree (QT/BT/TT) structure is adopted to divide a picture into square or rectangle blocks.

Besides QT/BT/TT, separate tree (a.k.a. Dual coding tree) is also adopted in VVC for I-frames. With separate tree, the coding block structure are signaled separately for the luma and chroma components.

In addition, the CU is set equal to PU and TU, except for blocks coded with a couple of specific coding methods (such as intra sub-partition prediction wherein PU is equal to TU, but smaller than CU, and sub-block transform for inter-coded blocks wherein PU is equal to CU, but TU is smaller than PU).

2.2.2 Affine Prediction Mode

In HEVC, only translation motion model is applied for motion compensation prediction (MCP). While in the real world, there are many kinds of motion, e.g. zoom in/out, rotation, perspective motions and the other irregular motions. In VVC, a simplified affine transform motion compensation prediction is applied with 4-parameter affine model and 6-parameter affine model. As shown FIG. 10, the affine motion field of the block is described by two control point motion vectors (CPMVs) for the 4-parameter affine model and 3 CPMVs for the 6-parameter affine model.

The motion vector field (MVF) of a block is described by the following equations with the 4-parameter affine model (wherein the 4-parameter are defined as the variables a, b, e and f) in equation (1) and 6-parameter affine model (therein the 4-parameter are defined as the variables a, b, c, d, e and f) in equation (2) respectively:

$\begin{matrix} \left\{ \begin{matrix} {{{mv}^{h}\left( {x,y} \right)} = {{{ax} - {by} + e} = {{\frac{\left( {{mv}_{1}^{h} - {mv}_{0}^{h}} \right)}{w}x} - {\frac{\left( {{mv}_{1}^{v} - {mv}_{0}^{v}} \right)}{w}y} + {mv}_{0}^{h}}}} \\ {{{mv}^{v}\left( {x,y} \right)} = {{{bx} + {ay} + f} = {{\frac{\left( {{mv}_{1}^{v} - {mv}_{0}^{v}} \right)}{w}x} + {\frac{\left( {{mv}_{1}^{h} - {mv}_{0}^{h}} \right)}{w}y} + {mv}_{0}^{v}}}} \end{matrix} \right. & (1) \\ \left\{ \begin{matrix} {{{mv}^{h}\left( {x,y} \right)} = {{{ax} + {cy} + e} = {{\frac{\left( {{mv}_{1}^{h} - {mv}_{0}^{h}} \right)}{w}x} + {\frac{\left( {{mv}_{2}^{h} - {mv}_{0}^{h}} \right)}{h}y} + {mv}_{0}^{h}}}} \\ {{{mv}^{v}\left( {x,y} \right)} = {{{bx} + {dy} + f} = {{\frac{\left( {{mv}_{1}^{v} - {mv}_{0}^{v}} \right)}{w}x} + {\frac{\left( {{mv}_{2}^{v} - {mv}_{0}^{v}} \right)}{h}y} + {mv}_{0}^{v}}}} \end{matrix} \right. & (2) \end{matrix}$

where (mv^(h) ₀, mv^(h) ₀) is motion vector of the top-left corner control point, and (mv^(h) ₁, mv^(h) ₁) is motion vector of the top-right corner control point and (mv^(h) ₂, mv^(h) ₂) is motion vector of the bottom-left corner control point, all of the three motion vectors are called control point motion vectors (CPMV), (x, y) represents the coordinate of a representative point relative to the top-left sample within current block and (mv^(h)(x,y), mv^(v)(x,y)) is the motion vector derived for a sample located at (x, y). The CP motion vectors may be signaled (like in the affine AMVP mode) or derived on-the-fly (like in the affine merge mode). w and h are the width and height of the current block. In practice, the division is implemented by right-shift with a rounding operation. In VTM, the representative point is defined to be the center position of a sub-block, e.g., when the coordinate of the left-top corner of a sub-block relative to the top-left sample within current block is (xs, ys), the coordinate of the representative point is defined to be (xs+2, ys+2). For each sub-block (i.e., 4×4 in VTM), the representative point is utilized to derive the motion vector for the whole sub-block.

In order to further simplify the motion compensation prediction, sub-block based affine transform prediction is applied. To derive motion vector of each M×N (both M and N are set to 4 in current VVC) sub-block, the motion vector of the center sample of each sub-block, as shown in FIG. 11, is calculated according to Equation (1) and (2), and rounded to 1/16 fraction accuracy. Then the motion compensation interpolation filters for 1/16-pel are applied to generate the prediction of each sub-block with derived motion vector. The interpolation filters for 1/16-pel are introduced by the affine mode.

After MCP, the high accuracy motion vector of each sub-block is rounded and saved as the same accuracy as the normal motion vector.

2.2.3 MERGE for Whole Block 2.2.3.1 Merge List Construction of Translational Regular Merge Mode 2.2.3.1.1 History-Based Motion Vector Prediction (HMVP)

Different from the merge list design, in VVC, the history-based motion vector prediction (HMVP) method is employed.

In HMVP, the previously coded motion information is stored. The motion information of a previously coded block is defined as an HMVP candidate. Multiple HMVP candidates are stored in a table, named as the HMVP table, and this table is maintained during the encoding/decoding process on-the-fly. The HMVP table is emptied when starting coding/decoding a new tile/LCU row/a slice. Whenever there is an inter-coded block and non-sub-block, non-TPM mode, the associated motion information is added to the last entry of the table as a new HMVP candidate. The overall coding flow is depicted in FIG. 12.

2.2.3.1.2. Regular Merge List Construction Process

The construction of the regular merge list (for translational motion) can be summarized according to the following sequence of steps:

-   -   Step 1: Derivation of spatial candidates     -   Step 2: Insertion of HMVP candidates     -   Step 3: Insertion of pairwise average candidates     -   Step 4: default motion candidates

HMVP candidates could be used in both AMVP and merge candidate list construction processes. FIG. 13 depicts. The modified merge candidate list construction process (shown in dotted pattern). When the merge candidate list is not full after the TMVP candidate insertion, HMVP candidates stored in the HMVP table could be utilized to fill in the merge candidate list. Considering that one block usually has a higher correlation with the nearest neighbourring block in terms of motion information, the HMVP candidates in the table are inserted in a descending order of indices. The last entry in the table is firstly added to the list, while the first entry is added in the end. Similarly, redundancy removal is applied on the HMVP candidates. Once the total number of available merge candidates reaches the maximal number of merge candidates allowed to be signaled, the merge candidate list construction process is terminated.

It is noted that all the spatial/temporal/HMVP candidate shall be coded with non-IBC mode. Otherwise, it is not allowed to be added to the regular merge candidate list.

HMVP table contains up to 5 regular motion candidates and each of them is unique.

2.2.3.1.2.1 Pruning Processes

A candidate is only added to the list if the corresponding candidate used for redundancy check has not the same motion information. Such comparison process is called pruning process.

The pruning process among the spatial candidates is dependent on the usage of TPM for current block.

When current block is coded without TPM mode (e.g., regular merge, MMVD, CIIP), the HEVC pruning process (i.e., five pruning) for the spatial merge candidates is utilized.

2.2.4 Triangular Prediction Mode (TPM)

In VVC, a triangle partition mode is supported for inter prediction. The triangle partition mode is only applied to CUs that are 8×8 or larger and are coded in merge mode but not in MMVD or CIIP mode. For a CU satisfying these conditions, a CU-level flag is signalled to indicate whether the triangle partition mode is applied or not.

When this mode is used, a CU is split evenly into two triangle-shaped partitions, using either the diagonal split or the anti-diagonal split, as depicted in FIG. 14. Each triangle partition in the CU is inter-predicted using its own motion; only uni-prediction is allowed for each partition, that is, each partition has one motion vector and one reference index. The uni-prediction motion constraint is applied to ensure that same as the conventional bi-prediction, only two motion compensated prediction are needed for each CU.

If the CU-level flag indicates that the current CU is coded using the triangle partition mode, a flag indicating the direction of the triangle partition (diagonal or anti-diagonal), and two merge indices (one for each partition) are further signalled. After predicting each of the triangle partitions, the sample values along the diagonal or anti-diagonal edge are adjusted using a blending processing with adaptive weights. This is the prediction signal for the whole CU and transform and quantization process will be applied to the whole CU as in other prediction modes. Finally, the motion field of a CU predicted using the triangle partition mode is stored in 4x4 units.

The regular merge candidate list is re-used for triangle partition merge prediction with no extra motion vector pruning. For each merge candidate in the regular merge candidate list, one and only one of its L0 or L1 motion vector is used for triangle prediction. In addition, the order of selecting the L0 vs. L1 motion vector is based on its merge index parity. With this scheme, the regular merge list can be directly used.

2.2.4.1 Merge List Construction Process for TPM

Basically, the regular merge list construction process is applied as proposed in JVET-N0340. However, some modifications are added.

Specifically, the followings are applied:

-   -   1) How to do the pruning process is dependent on the usage of         TPM for current block         -   If the current block is not coded with TPM, the HEVC 5             pruning applied to spatial merge candidates is invoked         -   Otherwise (if the current block is coded with TPM), full             pruning is applied when adding a new spatial merge             candidates. That is, B1 is compared to A1; B0 is compared to             A1 and B1; A0 is compared to A1, B1, and B0; B2 is compared             to A1, B1, A0, and B0.     -   2) The condition on whether to check of motion information from         B2 is dependent on the usage of TPM for current block         -   If the current block is not coded with TPM, B2 is accessed             and checked only when there are less than 4 spatial merge             candidates before checking B2.         -   Otherwise (if the current block is coded with TPM), B2 is             always accessed and checked regardless how many available             spatial merge candidates before adding B2.

2.2.4.2 Adaptive Weighting Process

After predicting each triangular prediction unit, an adaptive weighting process is applied to the diagonal edge between the two triangular prediction units to derive the final prediction for the whole CU. Two weighting factor groups are defined as follows:

-   1^(st) weighting factor group: {7/8, 6/8, 4/8, 2/8, 1/8} and {7/8,     4/8, 1/8} are used for the luminance and the chrominance samples,     respectively; -   2^(nd) weighting factor group: {7/8, 6/8, 5/8, 4/8, 3/8, 2/8, 1/8}     and {6/8, 4/8, 2/8} are used for the luminance and the chrominance     samples, respectively.

Weighting factor group is selected based on the comparison of the motion vectors of two triangular prediction units. The 2^(nd) weighting factor group is used when any one of the following condition is true:

-   -   the reference pictures of the two triangular prediction units         are different from each other     -   absolute value of the difference of two motion vectors'         horizontal values is larger than 16 pixels.     -   absolute value of the difference of two motion vectors' vertical         values is larger than 16 pixels.

Otherwise, the 1^(st) weighting factor group is used. An example is shown in FIG. 15.

2.2.4.3 Motion Vector Storage

The motion vectors (Mv1 and Mv2 in FIG. 16) of the triangular prediction units are stored in 4×4 grids. For each 4×4 grid, either uni-prediction or bi-prediction motion vector is stored depending on the position of the 4×4 grid in the CU. As shown in FIG. 16, uni-prediction motion vector, either Mv1 or Mv2, is stored for the 4×4 grid located in the non-weighted area (that is, not located at the diagonal edge). On the other hand, a bi-prediction motion vector is stored for the 4×4 grid located in the weighted area. The bi-prediction motion vector is derived from Mv1 and Mv2 according to the following rules:

-   -   1) In the case that Mv1 and Mv2 have motion vector from         different directions (L0 or L1), Mv1 and Mv2 are simply combined         to form the bi-prediction motion vector.     -   2) In the case that both Mv1 and Mv2 are from the same L0 (or         L1) direction,         -   If the reference picture of Mv2 is the same as a picture in             the L1 (or L0) reference picture list, Mv2 is scaled to the             picture. Mv1 and the scaled Mv2 are combined to form the             bi-prediction motion vector.         -   If the reference picture of Mv1 is the same as a picture in             the L1 (or L0) reference picture list, Mv1 is scaled to the             picture. The scaled Mv1 and Mv2 are combined to form the             bi-prediction motion vector.         -   Otherwise, only Mv1 is stored for the weighted area.

2.2.4.4 Syntax Tables, Semantics and Decoding Process for Merge Mode 7.3.5.1 General Slice Header Syntax

Descriptor slice_header( ) {  slice_pic_parameter_set_id ue(v)  if( rect_slice_flag || NumBricksInPic > 1 )   slice_address u(v)  if( !rect_slice_flag && !single_brick_per_slice_flag )   num_bricks_in_slice_minus1 ue(v)  slice_type ue(v) . . .  IF ( SLICE_TYPE != I ) {   if( sps_temporal_mvp_enabled_flag)    slice_temporal_mvp_enabled_flag u(1)  if( slice_type == B)    mvd_l1_zero_flag u(1)  if( cabac_init_present_flag)    cabac_init_flag u(1)   if( slice_temporal_mvp_enabled_flag) {    if( slice_type == B)     collocated_from_l0_flag u(1)   }   if( ( weighted_pred_flag && slice_type == P) ||    ( weighted_bipred_flag && slice_type == B ) )    pred_weight_table( )   SIX_MINUS_MAX_NUM_MERGE_CAND ue(v)   IF( SPS_AFFINE_ENABLED_FLAG)    FIVE_MINUS_MAX_NUM_SUBBLOCK_MERGE_CAND UE(V)   IF( SPS_FPEL_MMVD_ENABLED_FLAG)    SLICE_FPEL_MMVD_ENABLED_FLAG U(1)   IF( SPS_TRIANGLE_ENABLED_FLAG && MAXNUMMERGECAND >= 2 )    MAX_NUM_MERGE_CAND_MINUS_MAX_NUM_TRIANGLE_CAND UE(V)  } ELSE IF ( SPS_IBC_ENABLED_FLAG )   SIX_MINUS_MAX_NUM_MERGE_CAND ue(v)  slice_qp_delta se(v)  if( pps_slice_chroma_qp_offsets_present_flag ) {   slice_cb_qp_off_set se(v)   slice_cr_qp_offset se(v)  } . . .  byte_alignment( ) }

7.3.7.5 Coding Unit Syntax

Descriptor coding_unit( x0, y0, cbWidth, cb Height, tree Type ) {  if( slice_type !=I || sps_ibc_enabled_flag) {   if( treeType !=DUAL_TREE_CHROMA &&    !( cbWidth == 4 && cbHeight == 4 && !sps_ibc_enabled_flag))     cu_skip_flag[ x0 ][ y0 ] ae(v)   if( cu_skip_flag[ x0 ][ y0 ] == 0 && slice_type != I    && !( cbWidth == 4 && cbHeight == 4 ) )     pred_mode_flag ae(v)   if( ( ( slice_type == I && cu_skip_flag[ x0 ][ y0 ] ==0 ) ||    ( slice_type != I && ( CuPredMode[ x0 ][ y0 ] != MODE_INTRA ||    ( cbWidth == 4 && cbHeight == 4 && cu_skip_flag[ x0 ][ y0 ] == 0 ) ) ) ) &&     sps_ibc_enabled_flag && ( cbWidth != 128 || cbHeight != 128 ) )     pred_mode_ibc_flag ae(v)  }  if( CuPredMode[ x0 ][ y0 ] == MODE_INTRA) { . . .   }  } else if( treeType !=DUAL_TREE_CHROMA) { /* MODE_INTER or MODE_IBC */   if( cu_skip_flag[ x0 ][ y0 ] == 0)    general_merge_flag[ x0 ][ y0 ] ae(v)   if( general_merge_flag[ x0 ][ y0 ]) {    merge_data( x0, y0, cbWidth, cbHeight)   } ELSE IF( CUPREDMODE [ X0 ][ Y0 ] == MODE_IBC ) {    MVD_CODING( X0, Y0, 0, 0 )    MVP_L0_FLAG[ X0 ][ Y0 ] AE(V)    IF( SPS_AMVR_ENABLED_FLAG &&     ( MVDL0[ X0 ][ Y0 ][ 0 ] != 0 || MVDL0[ X0 ][ Y0 ][ 1 ] != 0 ) ) {     AMVR_PRECISION_FLAG[ X0 ][ Y0 ] AE(V)    }   } else {    if( slice_type == B)     inter_pred_idc[ x0 ][ y0 ] ae(v)    if( sps_affine_enabled_flag && cbWidth >=16 && cbHeight >=16 ) {     inter_affine_flag[ x0 ][ y0 ] ae(v)     if( sps_affine_type_flag && inter_affine_flag[ x0 ][ y0 ] )      cu_affine_type flag[ x0 ][ y0 ] ae(v)    }    if( sps_smvd_enabled_flag && inter_pred_idc[ x0 ][ y0 ] == PRED_BI &&     !inter_affine_flag[ x0 ][ y0 ] && RefIdxSymL0 >−1 && RefIdxSymL1 >−1 )     sym_mvd_flag[ x0 ][ y0 ] ae(v) . . .  } }

7.3.7.7 Merge Data Syntax

Descriptor merge_data( x0, y0, cbWidth, cbHeight) {  IF ( CUPREDMODE [ X0 ][ Y0 ] == MODE_IBC ) {   IF( MAXNUMMERGECAND > 1 )    MERGE_IDX[ X0 ][ Y0 ] AE(V)  } ELSE {   if( sps_mmvd_enabled_flag || cbWidth * cbHeight !=32 )    regular_merge_flag[ x0 ][ y0 ] ae(v)   if ( regular_merge_flag[ x0 ][ y0 ] == 1){    if( MaxNumMergeCand > 1)     merge_idx[ x0 ][ y0 ] ae(v)   } else {    if( sps_mmvd_enabled_flag && cbWidth* cbHeight !=32 )     mmvd_merge_flag[ x0 ][ y0 ] ae(v)    if( mmvd_merge_flag[ x0 ][ y0 ] == 1 ) {     if( MaxNumMergeCand> 1 )      mmvd_cand_flag[ x0 ][ y0 ] ae(v)      mmvd_distance_idx[ x0 ][ y0 ] ae(v)      mmvd_direction_idx[ x0 ][ y0 ] ae(v)     } else {      if( MaxNumSubblockMergeCand> 0 && cbWidth >=8 && cbHeight >=8 )      merge_subblock_flag[ x0 ][ y0 ] ae(v)      if( merge_subblock_flag[ x0 ][ y0 ] == 1) {      if( MaxNumSubblockMergeCand> 1 )       merge_subblock_idx[ x0 ][ y0 ] ae(v)      } else {      if( sps_ciip_enabled_flag && cu_skip_flag[ x0 ][ y0 ] == 0 &&       ( cbWidth * cbHeight ) >=64 && cbWidth < 128 && cbHeight < 128 ) {       ciip_flag[ x0 ][ y0 ] ae(v)      if( ciip_flag[ x0 ][ y0 ] && MaxNumMergeCand> 1 )       merge_idx[ x0 ][ y0 ] ae(v)      }      if( MergeTriangleFlag[ x0 ][ y0 ] ) {       merge_triangle_split_dir[ x0 ][ y0 ] ae(v)       merge_triangle_idx0[ x0 ][ y0 ] ae(v)       merge_triangle_idx1[ x0 ][ y0 ] ae(v)      }     }    }   }  } }

7.4.6.1 General Slice Header Semantics

six_minus_max_num_merge_cand specifies the maximum number of merging motion vector prediction (MVP) candidates supported in the slice subtracted from 6. The maximum number of merging MVP candidates, MaxNumMergeCand is derived as follows:

MaxNumMergeCand=6−six_minus_max_num_merge_cand  (7-57)

The value of MaxNumMergeCand shall be in the range of 1 to 6, inclusive.

-   five_minus_max_num_subblock_merge_cand specifies the maximum number     of subblock-based merging motion vector prediction (MVP) candidates     supported in the slice subtracted from 5. When     five_minus_max_num_subblock_merge_cand is not present, it is     inferred to be equal to 5−sps_sbtmvp_enabled_flag. The maximum     number of subblock-based merging MVP candidates,     MaxNumSubblockMergeCand is derived as follows:

MaxNumSubblockMergeCand=5−five_minus_max_num_subblock_merge_cand  (7-58)

The value of MaxNumSubblockMergeCand shall be in the range of 0 to 5, inclusive.

7.4.8.5 Coding Unit Semantics

-   pred_mode _flag equal to 0 specifies that the current coding unit is     coded in inter prediction mode. pred_mode_flag equal to 1 specifies     that the current coding unit is coded in intra prediction mode.

When pred_mode_flag is not present, it is inferred as follows:

-   If cbWidth is equal to 4 and cbHeight is equal to 4, pred_mode_flag     is inferred to be equal to 1. -   Otherwise, pred_mode_flag is inferred to be equal to 1 when decoding     an I slice, and equal to 0 when decoding a P or B slice,     respectively.

The variable CuPredMode[x][y] is derived as follows for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1:

-   If pred_mode_flag is equal to 0, CuPredMode[x][y] is set equal to     MODE_INTER. -   Otherwise (pred_mode_flag is equal to 1), CuPredMode[x][y] is set     equal to MODE_INTRA. -   pred_mode_ibc_flag equal to 1 specifies that the current coding unit     is coded in IBC prediction mode. pred_mode_ibc_flag equal to 0     specifies that the current coding unit is not coded in IBC     prediction mode.

When pred_mode_ibc_flag is not present, it is inferred as follows:

-   If cu_skip_flag[x0][y0] is equal to 1, and cbWidth is equal to 4,     and cbHeight is equal to 4, pred_mode_ibc_flag is inferred to be     equal 1. -   Otherwise, if both cbWidth and cbHeight are equal to 128,     pred_mode_ibc_flag is inferred to be equal to 0. -   Otherwise, pred_mode_ibc_flag is inferred to be equal to the value     of sps_ibc_enabled_flag when decoding an I slice, and 0 when     decoding a P or B slice, respectively.

When pred_mode_ibc_flag is equal to 1, the variable CuPredMode[x][y] is set to be equal to MODE_IBC for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1.

-   general_merge_flag[x0][y0] specifies whether the inter prediction     parameters for the current coding unit are inferred from a     neighbouring inter-predicted partition. The array indices x0, y0     specify the location (x0, y0) of the top-left luma sample of the     considered coding block relative to the top-left luma sample of the     picture.

When general_merge_flag[x0][y0] is not present, it is inferred as follows:

-   If cu_skip_flag[x0][y0] is equal to 1, general_merge_flag[x0][y0] is     inferred to be equal to 1. -   Otherwise, general_merge_flag[x0][y0] is inferred to be equal to 0. -   mvp_l0_flag[x0][y0] specifies the motion vector predictor index of     list 0 where x0, y0 specify the location (x0, y0) of the top-left     luma sample of the considered coding block relative to the top-left     luma sample of the picture.

When mvp_l0_flag[x0][y0] is not present, it is inferred to be equal to 0.

-   mvp_l1_flag[x0][y0] has the same semantics as mvp_l0_flag, with l0     and list 0 replaced by l1 and list 1, respectively. -   inter_pred_id[x0][y0] specifies whether list0, list1, or     bi-prediction is used for the current coding unit according to Table     7-10. The array indices x0, y0 specify the location (x0, y0) of the     top-left luma sample of the considered coding block relative to the     top-left luma sample of the picture.

TABLE 7-10 Name association to inter prediction mode Name of inter_pred_idc inter_pred_idc ( cbWidth + cbHeight ) > 12 ( cbWidth + cbHeight ) = = 12 ( cbWidth + cbHeight ) = = 8 0 PRED_L0 PRED_L0 n.a. 1 PRED_L1 PRED_L1 n.a. 2 PRED_BI n.a. n.a.

When inter_pred_idc[x0][y0] is not present, it is inferred to be equal to PRED_L0.

7.4.8.7 Merge Data Semantics

-   regular_merge_flag[x0][y0] equal to 1 specifies that regular merge     mode is used to generate the inter prediction parameters of the     current coding unit. The array indices x0, y0 specify the location     (x0, y0) of the top-left luma sample of the considered coding block     relative to the top-left luma sample of the picture.

When regular_merge_flag[x0][y0] is not present, it is inferred as follows:

-   If all the following conditions are true, regular_merge_flag[x0][y0]     is inferred to be equal to 1:     -   sps_mmvd_enabled_flag is equal to 0.     -   general_merge_flag[x0][y0] is equal to 1.     -   cbWidth*cbHeight is equal to 32. -   Otherwise, regular_merge_flag[x0][y0] is inferred to be equal to 0. -   mmvd_merge_flag[x0][y0] equal to 1 specifies that merge mode with     motion vector difference is used to generate the inter prediction     parameters of the current coding unit. The array indices x0, y0     specify the location (x0, y0) of the top-left luma sample of the     considered coding block relative to the top-left luma sample of the     picture.

When mmvd_merge_flag[x0][y0] is not present, it is inferred as follows:

-   If all the following conditions are true, mmvd_merge_flag[x0][y0] is     inferred to be equal to 1:     -   sps_mmvd_enabled_flag is equal to 1.     -   general_merge_flag[x0][y0] is equal to 1.     -   cbWidth*cbHeight is equal to 32.     -   regular_merge_flag[x0][y0] is equal to 0. -   Otherwise, mmvd_merge_flag[x0][y0] is inferred to be equal to 0. -   mmvd_cand_flag[x0][y0] specifies whether the first (0) or the     second (1) candidate in the merging candidate list is used with the     motion vector difference derived from mmvd_distance_idx[x0][y0] and     mmvd_direction_idx[x0][y0]. The array indices x0, y0 specify the     location (x0, y0) of the top-left luma sample of the considered     coding block relative to the top-left luma sample of the picture.

When mmvd_cand_flag[x0][y0] is not present, it is inferred to be equal to 0.

-   mmvd_distance_idx[x0][y0] specifies the index used to derive     MmvdDistance[x0][y0] as specified in Table 7-12. The array indices     x0, y0 specify the location (x0, y0) of the top-left luma sample of     the considered coding block relative to the top-left luma sample of     the picture.

TABLE 7-12 Specification of MmvdDistance[ x0 ][ y0 ] based on mmvd_distance_idx[ x0 ][ y0 ]. MmvdDistance[ x0 ][ y0 ] mmvd_distance_ slice_fpel_mmvd_enabled_flag = = idx[ x0 ][ y0 ] 0 slice_fpel_mmvd_enabled_flag = = 1 0 1 4 1 2 8 2 4 16 3 8 32 4 16 64 5 32 128 6 64 256 7 128 512

-   mmvd_direction_idx[x0][y0] specifies index used to derive     MmvdSign[x0][y0] as specified in Table 7-13. The array indices x0,     y0 specify the location (x0, y0) of the top-left luma sample of the     considered coding block relative to the top-left luma sample of the     picture.

TABLE 7-13 Specification of MmvdSign[ x0 ][ y0 ] based on mmvd_direction_idx[ x0 ][ y0 ] mmvd_direction_idx MmvdSign MmvdSign [ x0 ][ y0 ] [ x0 ][ y0 ][0] [ x0 ][ y0 ][1] 0 +1 0 1 −1 0 2 0 +1 3 0 −1

Both components of the merge plus MVD offset MmvdOffset[x0][y0] are derived as follows:

MmvdOffset[x0][y0][0]=(MmvdDistance[x0][y0] <<2)*MmvdSign[x0][y0][0]  (7-124)

MmvdOffset[x0][y0][1]=(MmvdDistance[x0][y0] <<2)*MmvdSign[x0][y0][1]  (7-125)

-   merge_subblock_flag[x0][y0] specifies whether the subblock-based     inter prediction parameters for the current coding unit are inferred     from neighbouring blocks. The array indices x0, y0 specify the     location (x0, y0) of the top-left luma sample of the considered     coding block relative to the top-left luma sample of the picture.     When merge_subblock_flag[x0][y0] is not present, it is inferred to     be equal to 0. -   merge_subblock_idx[x0][y0] specifies the merging candidate index of     the subblock-based merging candidate list where x0, y0 specify the     location (x0, y0) of the top-left luma sample of the considered     coding block relative to the top-left luma sample of the picture.

When merge_subblock_idx[x0][y0] is not present, it is inferred to be equal to 0.

-   ciip_flag[x0][y0] specifies whether the combined inter-picture merge     and intra-picture prediction is applied for the current coding unit.     The array indices x0, y0 specify the location (x0, y0) of the     top-left luma sample of the considered coding block relative to the     top-left luma sample of the picture.

When ciip_flag[x0][y0] is not present, it is inferred to be equal to 0.

When ciip_flag[x0][y0] is equal to 1, the variable IntraPredModeY[x][y] with x=xCb . . . xCb+cbWidth−1 and y=yCb . . . yCb+cbHeight−1 is set to be equal to INTRA_PLANAR.

The variable MergeTriangleFlag[x0][y0], which specifies whether triangular shape based motion compensation is used to generate the prediction samples of the current coding unit, when decoding a B slice. is derived as follows:

-   If all the following conditions are true, MergeTriangleFlag[x0][y0]     is set equal to 1:     -   sps_triangle_enabled_flag is equal to 1.     -   slice_type is equal to B.     -   general_merge_flag[x0][y0] is equal to 1.     -   MaxNumTriangleMergeCand is greater than or equal to 2.     -   cbWidth*cbHeight is greater than or equal to 64.     -   regular_merge_flag[x0][y0] is equal to 0.     -   mmvd_merge_flag[x0][y0] is equal to 0.     -   merge_subblock_flag[x0][y0] is equal to 0.     -   ciip_flag[x0][y0] is equal to 0. -   Otherwise, MergeTriangleFlag[x0][y0] is set equal to 0. -   merge_triangle_split_dir[x0][y0] specifies the splitting direction     of merge triangle mode. The array indices x0, y0 specify the     location (x0, y0) of the top-left luma sample of the considered     coding block relative to the top-left luma sample of the picture.

When merge_triangle_split_dir[x0][y0] is not present, it is inferred to be equal to 0.

-   merge_triangle_idx0[x0][y0] specifies the first merging candidate     index of the triangular shape based motion compensation candidate     list where x0, y0 specify the location (x0, y0) of the top-left luma     sample of the considered coding block relative to the top-left luma     sample of the picture.

When merge_triangle_idx0[x0][y0] is not present, it is inferred to be equal to 0.

-   merge_triangle_idx1[x0][y0] specifies the second merging candidate     index of the triangular shape based motion compensation candidate     list where x0, y0 specify the location (x0, y0) of the top-left luma     sample of the considered coding block relative to the top-left luma     sample of the picture.

When merge_triangle_idx1[x0][y0] is not present, it is inferred to be equal to 0.

-   merge_idx[x0][y0] specifies the merging candidate index of the     merging candidate list where x0, y0 specify the location (x0, y0) of     the top-left luma sample of the considered coding block relative to     the top-left luma sample of the picture.

When merge_idx[x0][y0] is not present, it is inferred as follows:

-   If mmvd_merge_flag[x0][y0] is equal to 1, merge_idx[x0][y0] is     inferred to be equal to mmvd_cand_flag[x0][y0]. -   Otherwise (mmvd_merge_flag[x0][y0] is equal to 0), merge_idx[x0][y0]     is inferred to be equal to 0.

2.2.4.4.1 Decoding Process

The decoding process as provided in the JVET-N0340 is defined as follows:

8.5.2.2 Derivation Process for Luma Motion Vectors for Merge Mode

This process is only invoked when general_merge_flag[xCb] [yCb] is equal to 1, where (xCb, yCb) specify the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture.

Inputs to this process are:

-   a luma location (xCb, yCb) of the top-left sample of the current     luma coding block relative to the top-left luma sample of the     current picture, -   a variable cbWidth specifying the width of the current coding block     in luma samples, -   a variable cbHeight specifying the height of the current coding     block in luma samples.

Outputs of this process are:

-   the luma motion vectors in 1/16 fractional-sample accuracy     mvL0[0][0] and mvL1[0][0], -   the reference indices refIdxL0 and refIdxL1, -   the prediction list utilization flags predFlagL0[0][0] and     predFlagL1[0][0], -   the bi-prediction weight index bcwIdx. -   the merging candidate list mergeCandList.

The bi-prediction weight index bcwIdx is set equal to 0.

The motion vectors mvL0[0][0] and mvL1[0][0], the reference indices refIdxL0 and refIdxL1 and the prediction utilization flags predFlagL0[0][0] and predFlagL1[0][0] are derived by the following ordered steps:

-   -   1. The derivation process for spatial merging candidates from         neighbouring coding units as specified in clause 8.5.2.3 is         invoked with the luma coding block location (xCb, yCb), the luma         coding block width cbWidth, and the luma coding block height         cbHeight as inputs, and the output being the availability flags         availableFlagA0, availableFlagA₁, availableFlagB₀,         availableFlagB₁ and availableFlagB₂, the reference indices         refIdxLXA₀, refIdxLXA₁, refIdxLXB₀, refIdxLXB₁ and refIdxLXB₂,         the prediction list utilization flags predFlagLXA₀,         predFlagLXA₁, predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂, and         the motion vectors mvLXA₀, mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂,         with X being 0 or 1, and the bi-prediction weight indices         bcwIdxA₀, bcwIdxA₁, bcwIdxB₀, bcwIdxB₁, bcwIdxB₂.     -   2. The reference indices, refIdxLXCol, with X being 0 or 1, and         the bi-prediction weight index bcwIdxCol for the temporal         merging candidate Col are set equal to 0.     -   3. The derivation process for temporal luma motion vector         prediction as specified in in clause 8.5.2.11 is invoked with         the luma location (xCb, yCb), the luma coding block width         cbWidth, the luma coding block height cbHeight and the variable         refIdxL0Col as inputs, and the output being the availability         flag availableFlagL0Col and the temporal motion vector mvL0Col.         The variables availableFlagCol, predFlagL0Col and predFlagL1Col         are derived as follows:

availableFlagCol=availableFlagL0Col  (8-263)

predFlagL0Col=availableFlagL0Col  (8-264)

predFlagL1Col=0  (8-265)

-   -   4. When slice_type is equal to B, the derivation process for         temporal luma motion vector prediction as specified in clause         8.5.2.11 is invoked with the luma location (xCb, yCb), the luma         coding block width cbWidth, the luma coding block height         cbHeight and the variable refIdxL1Col as inputs, and the output         being the availability flag availableFlagL1Col and the temporal         motion vector mvL1Col. The variables availableFlagCol and         predFlagL1Col are derived as follows:

availableFlagCol=availableFlagL0Col||availableFlagL1Col  (8-266)

predFlagL1Col=availableFlagL1Col  (8-267)

-   -   5. The merging candidate list, mergeCandList, is constructed as         follows:         i=0

if(availableFlagA ₁)mergeCandList[i++]=A ₁

if(availableFlagB ₁)mergeCandList[i++]=B ₁

if(availableFlagB ₀)mergeCandList[i++]=B ₀

if(availableFlagA ₀)mergeCandList[i++]=A ₀

if(availableFlagB ₂)mergeCandList[i++]=B ₂

if(availableFlagCol)mergeCandList[i++]=Col  (8-268)

-   -   6. The variable numCurrMergeCand and numOrigMergeCand are set         equal to the number of merging candidates in the mergeCandList.     -   7. When numCurrMergeCand is less than (MaxNumMergeCand−1) and         NumHmvpCand is greater than 0, the following applies:         -   The derivation process of history-based merging candidates             as specified in 8.5.2.6 is invoked with mergeCandList and             numCurrMergeCand as inputs, and modified mergeCandList and             numCurrMergeCand as outputs.         -   numOrigMergeCand is set equal to numCurrMergeCand.     -   8. When numCurrMergeCand is less than MaxNumMergeCand and         greater than 1, the following applies:         -   The derivation process for pairwise average merging             candidate specified in clause 8.5.2.4 is invoked with             mergeCandList, the reference indices refIdxL0N and             refIdxL1N, the prediction list utilization flags predFlagL0N             and predFlagL1N, the motion vectors mvL0N and mvL1N of every             candidate N in mergeCandList, and numCurrMergeCand as             inputs, and the output is assigned to mergeCandList,             numCurrMergeCand, the reference indices refIdxL0avgCand and             refIdxLlavgCand, the prediction list utilization flags             predFlagL0avgCand and predFlagL1avgCand and the motion             vectors mvL0avgCand and mvL1avgCand of candidate avgCand             being added into mergeCandList. The bi-prediction weight             index bcwIdx of candidate avgCand being added into             mergeCandList is set equal to 0.         -   numOrigMergeCand is set equal to numCurrMergeCand.     -   9. The derivation process for zero motion vector merging         candidates specified in clause 8.5.2.5 is invoked with the         mergeCandList, the reference indices refIdxL0N and refIdxL1N,         the prediction list utilization flags predFlagL0N and         predFlagL1N, the motion vectors mvL0N and mvL1N of every         candidate N in mergeCandList and numCurrMergeCand as inputs, and         the output is assigned to mergeCandList, numCurrMergeCand, the         reference indices refIdxL0zeroCand_(m) and refIdxL1zeroCand_(m),         the prediction list utilization flags predFlagL0zeroCand_(m) and         predFlagL1zeroCand_(m) and the motion vectors mvL0zeroCand_(m)         and mvL1zeroCand_(m) of every new candidate zeroCand_(m) being         added into mergeCandList. The bi-prediction weight index bcwIdx         of every new candidate zeroCand_(m) being added into         mergeCandList is set equal to 0. The number of candidates being         added, numZeroMergeCand, is set equal to         (numCurrMergeCand−numOrigMergeCand). When numZeroMergeCand is         greater than 0, m ranges from 0 to numZeroMergeCand−1,         inclusive.     -   10. The following assignments are made with N being the         candidate at position merge_idx[xCb][yCb] in the merging         candidate list mergeCandList         (N=mergeCandList[merge_idx[xCb][yCb]]) and X being replaced by 0         or 1:

refIdxLX=refIdxLXN  (8-269)

predFlagLX[0][0]=predFlagLXN  (8-270)

mvLX[0][0][0]=mvLXN[0]  (8-271)

mvLX[0][0][1]=mvLXN[1]  (8-272)

bcwIdx=bcwIdxN  (8-273)

-   -   11. When mmvd_merge_flag[xCb][yCb] is equal to 1, the following         applies:         -   The derivation process for merge motion vector difference as             specified in 8.5.2.7 is invoked with the luma location (xCb,             yCb), the reference indices refIdxL0, refIdxL1 and the             prediction list utilization flags predFlagL0[0][0] and             predFlagL1[0][0] as inputs, and the motion vector             differences mMvdL0 and mMvdL1 as outputs.         -   The motion vector difference mMvdLX is added to the merge             motion vectors mvLX for X being 0 and 1 as follows:

mvLX[0][0][0]+=mMvdLX[0]  (8-274)

mvLX[0][0][1]+=mMvdLX[1]  (8-275)

mvLX[0][0][0]=Clip3(−2¹⁷, 2¹⁷−1, mvLX[0][0][0])  (8-276)

mvLX[0][0][1]=Clip3(−2¹⁷, 2¹⁷−1, mvLX[0][0][1])  (8-277)

8.5.2.3 Derivation Process for Spatial Merging Candidates

Inputs to this process are:

-   a luma location (xCb, yCb) of the top-left sample of the current     luma coding block relative to the top-left luma sample of the     current picture, -   a variable cbWidth specifying the width of the current coding block     in luma samples, -   a variable cbHeight specifying the height of the current coding     block in luma samples.

Outputs of this process are as follows, with X being 0 or 1:

-   the availability flags availableFlagA₀, availableFlagA₁,     availableFlagB₀, availableFlagB₁ and availableFlagB₂ of the     neighbouring coding units, -   the reference indices refIdxLXA₀, refIdxLXA₁, refIdxLXB₀, refIdxLXB₁     and refIdxLXB₂ of the neighbouring coding units, -   the prediction list utilization flags predFlagLXA₀, predFlagLXA₁,     predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂ of the neighbouring     coding units, -   the motion vectors in 1/16 fractional-sample accuracy mvLXA₀,     mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂ of the neighbouring coding units, -   the bi-prediction weight indices gbiIdxA₀, gbiIdxA₁, gbiIdxB₀,     gbiIdxB₁, and gbiIdxB₂.

For the derivation of availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁ the following applies:

-   The luma location (xNbA₁, yNbA₁) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbHeight−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₁, yNbA₁) as inputs, and the output is assigned to the block     availability flag available/⁶i′. -   The variables availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁     are derived as follows:     -   If availableA₁ is equal to FALSE, availableFlagA₁ is set equal         to 0, both components of mvLXA₁ are set equal to 0, refIdxLXA₁         is set equal to −1 and predFlagLXA₁ is set equal to 0, with X         being 0 or 1, and gbiIdxA₁ is set equal to 0.     -   Otherwise, availableFlagA₁ is set equal to 1 and the following         assignments are made:

mvLXA ₁=MvLX[xNbA ₁][yNbA ₁]  (8-294)

refIdxLXA ₁=RefIdxLX[xNbA ₁][yNbA ₁]  (8-295)

predFlagLXA ₁=PredFlagLX[xNbA ₁][yNbA ₁]  (8-296)

gbiIdxA ₁ =GbiIdx[xNbA ₁][yNbA ₁]  (8-297)

For the derivation of availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁ the following applies:

-   The luma location (xNbB₁, yNbB₁) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth−1, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₁, yNbB₁) as inputs, and the output is assigned to the block     availability flag availableB₁. -   The variables availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₁ is set equal to 0, both components of mvLXB₁ are         set equal to 0, refIdxLXB₁ is set equal to −1 and predFlagLXB₁         is set equal to 0, with X being 0 or 1, and gbiIdxB₁ is set         equal to 0:         -   availableB₁ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₁, yNbB₁) have the same motion vectors and             the same reference indices.     -   Otherwise, availableFlagB₁ is set equal to 1 and the following         assignments are made:

mvLXB ₁=MvLX[xNbB ₁][yNbB ₁]  (8-298)

refIdxLXB ₁=RefIdxLX[xNbB ₁][yNbB ₁]  (8-299)

predFlagLXB ₁=PredFlagLX[xNbB ₁][yNbB ₁]  (8-300)

gbiIdxB ₁ =GbiIdx[xNbB ₁][yNbB ₁]  (8-301)

For the derivation of availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀ the following applies:

-   The luma location (xNbB₀, yNbB₀) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₀, yNbB₀) as inputs, and the output is assigned to the block     availability flag availableB₀. -   The variables availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₀ is set equal to 0, both components of mvLXB₀ are         set equal to 0, refIdxLXB₀ is set equal to −1 and predFlagLXB₀         is set equal to 0, with X being 0 or 1, and gbiIdxB₀ is set         equal to 0:         -   availableB₀ is equal to FALSE.         -   availableB₁ is equal to TRUE and the lumalocations(xNbB₁,             yNbB₁) and (xNbB₀, yNbB₀) have the same motion vectors and             the same reference indices.         -   availableA₁ is equal to TRUE, the luma locations (xNbA₁,             yNbA₁) and (xNbB₀, yNbB₀) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.     -   Otherwise, availableFlagB₀ is set equal to 1 and the following         assignments are made:

mvLXB ₀=MvLX[xNbB ₀][yNbB ₀]  (8-302)

refIdxLXB ₀=RefIdxLX[xNbB ₀][yNbB ₀]  (8-303)

predFlagLXB ₀=PredFlagLX[xNbB ₀][yNbB ₀]  (8-304)

gbiIdxB ₀ =GbiIdx[xNbB ₀][yNbB ₀]  (8-305)

For the derivation of availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀ the following applies:

-   The luma location (xNbA₀, yNbA₀) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbWidth). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₀, yNbA₀) as inputs, and the output is assigned to the block     availability flag availableA₀. -   The variables availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagA₀ is set equal to 0, both components of mvLXA₀ are         set equal to 0, refIdxLXA₀ is set equal to −1 and predFlagLXA₀         is set equal to 0, with X being 0 or 1, and gbiIdxA₀ is set         equal to 0:         -   availableA₀ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE, the luma locations (xNbB₁,             yNbB₁) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.     -   Otherwise, availableFlagA₀ is set equal to 1 and the following         assignments are made:

mvLXA ₀=MvLX[xNBA ₀][yNbA ₀]  (8-306)

refIdxLXA ₀=RefIdxLX[xNbA ₀][yNbA ₀]  (8-307)

predFlagLXA ₀=PredFlagLX[xNbA ₀][yNbA ₀]  (8-308)

gbiIdxA ₀ =GbiIdx[xNbA ₀][yNbA ₀]  (8-309)

For the derivation of availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂ the following applies:

-   The luma location (xNbB₂, yNbB₂) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb −1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₂, yNbB₂) as inputs, and the output is assigned to the block     availability flag availableB₂. -   The variables availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₂ is set equal to 0, both components of mvLXB₂ are         set equal to 0, refIdxLXB₂ is set equal to −1 and predFlagLXB₂         is set equal to 0, with X being 0 or 1, and gbiIdxB₂ is set         equal to 0:         -   availableB₂ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE and the luma locations (xNbB₁,             yNbB₁) and(xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.         -   availableA₀ is equal to TRUE, the luma locations (xNbA₀,             yNbA₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.         -   availableFlagA₀+availableFlagA₁+availableFlagB₀+availableFlagB₁             is equal to 4 and merge_triangle_flag[xCb][yCb] is equal to             0.     -   Otherwise, availableFlagB₂ is set equal to 1 and the following         assignments are made:

mvLXB ₂=MvLX[xNbB ₂][yNbB ₂]  (8-310)

refIdxLXB ₂=RefIdxLX[xNbB ₂][yNbB ₂]  8-311)

predFlagLXB ₂=PredFlagLX[xNbB ₂][yNbB ₂]  (8-312)

gbiIdxB ₂ =GbiIdx[xNbB ₂][yNbB ₂]  (8-313)

2.2.5 MMVD

In JVET-L0054, ultimate motion vector expression (UMVE, also known as MMVD) is presented. UMVE is used for either skip or merge modes with a proposed motion vector expression method.

UMVE re-uses merge candidate as same as those included in the regular merge candidate list in VVC. Among the merge candidates, a base candidate can be selected, and is further expanded by the proposed motion vector expression method.

UMVE provides a new motion vector difference (MVD) representation method, in which a starting point, a motion magnitude and a motion direction are used to represent a MVD.

This proposed technique uses a merge candidate list as it is. But only candidates which are default merge type (MRG_TYPE_DEFAULT_N) are considered for UMVE's expansion.

Base candidate index defines the starting point. Base candidate index indicates the best candidate among candidates in the list as follows.

TABLE 4 Base candidate IDX Base candidate IDX 0 1 2 3 N^(th) MVP 1^(st) MVP 2^(nd) MVP 3^(rd) MVP 4^(th) MVP

If the number of base candidate is equal to 1, Base candidate IDX is not signaled.

Distance index is motion magnitude information. Distance index indicates the pre-defined distance from the starting point information. Pre-defined distance is as follows:

TABLE 5 Distance IDX Distance IDX 0 1 2 3 4 5 6 7 Pixel 1/4- 1/2- 1- 2- 4- 8- 16- 32- distance pel pel pel pel pel pel pel pel

Direction index represents the direction of the MVD relative to the starting point. The direction index can represent of the four directions as shown below.

TABLE 6 Direction IDX Direction IDX 00 01 10 11 x-axis + − N/A N/A y-axis N/A N/A + −

UMVE flag is signaled right after sending a skip flag or merge flag. If skip or merge flag is true, UMVE flag is parsed. If UMVE flag is equal to 1, UMVE syntaxes are parsed. But, if not 1, AFFINE flag is parsed. If AFFINE flag is equal to 1, that is AFFINE mode, But, if not 1, skip/merge index is parsed for VTM's skip/merge mode.

Additional line buffer due to UMVE candidates is not needed. Because a skip/merge candidate of software is directly used as a base candidate. Using input UMVE index, the supplement of MV is decided right before motion compensation. There is no need to hold long line buffer for this.

In current common test condition, either the first or the second merge candidate in the merge candidate list could be selected as the base candidate.

UMVE is also known as Merge with MV Differences (MMVD).

2.2.6 Combined Intra-Inter Prediction (CIIP)

In JVET-L0100, multi-hypothesis prediction is proposed, wherein combined intra and inter prediction is one way to generate multiple hypotheses.

When the multi-hypothesis prediction is applied to improve intra mode, multi-hypothesis prediction combines one intra prediction and one merge indexed prediction. In a merge CU, one flag is signaled for merge mode to select an intra mode from an intra candidate list when the flag is true. For luma component, the intra candidate list is derived from only one intra prediction mode, i. e., planar mode. The weights applied to the prediction block from intra and inter prediction are determined by the coded mode (intra or non-intra) of two neighboring blocks (A1 and B1).

2.2.7 MERGE for Sub-Block-Based Technologies

It is suggested that all the sub-block related motion candidates are put in a separate merge list in addition to the regular merge list for non-sub block merge candidates.

The sub-block related motion candidates are put in a separate merge list is named as ‘sub-block merge candidate list’.

In one example, the sub-block merge candidate list includes ATMVP candidate and affine merge candidates.

The sub-block merge candidate list is filled with candidates in the following order:

-   -   a. ATMVP candidate (maybe available or unavailable);     -   b. Affine merge lists (including Inherited Affine candidates;         and Constructed Affine candidates)     -   c. Padding as zero MV 4-parameter affine model

2.2.7.1.1 ATMVP (aka Sub-Block Temporal Motion Vector Predictor, SbTMVP)

Basic idea of ATMVP is to derive multiple sets of temporal motion vector predictors for one block. Each sub-block is assigned with one set of motion information. When an ATMVP merge candidate is generated, the motion compensation is done in 8x8 level instead of the whole block level.

In current design, ATMVP predicts the motion vectors of the sub-CUs within a CU in two steps which are described in the following two sub-sections 2.2.7.1.1.1 and 2.2.7.1.1.2, respectively.

2.2.7.1.1.1 Derivation of Initialized Motion Vector

Denote the initialized motion vector by tempMv. When block A1 is available and non-intra coded (i.e., coded with inter or IBC mode), the following is applied to derive the initialized motion vector.

-   If all of the following conditions are true, tempMv is set equal to     the motion vector of block A1 from list 1, denoted by mvL1A₁:     -   Reference picture index of list 1 is available (not equal to         −1), and it has the same POC value as the collocated picture         (i.e., DiffPicOrderCnt(ColPic, RefPicList[1][refIdxL1A₁]) is         equal to 0),     -   All reference pictures are with no larger POC compared to the         current picture (i.e., DiffPicOrderCnt(aPic, currPic) is less         than or equal to 0 for every picture aPic in every reference         picture list of the current slice),     -   Current slice is equal to B slice,     -   collocated_from_l0_flag is equal to 0. -   Otherwise if all of the following conditions are true, tempMv is set     equal to the motion vector of block A1 from list 0, denoted by     mvL0A₁:     -   Reference picture index of list 0 is available (not equal to         −1),     -   it has the same POC value as the collocated picture (i.e.,         DiffPicOrderCnt(ColPic, RefPicList[0][refIdxL0A₁]) is equal to         0). -   Otherwise, zero motion vector is used as the initialized MV.

A corresponding block (with center position of current block plus the rounded MV, clipped to be in certain ranges in necessary) is identified in the collocated picture signaled at the slice header with the initialized motion vector.

If the block is inter-coded, then go to the 2^(nd) step. Otherwise, the ATMVP candidate is set to be NOT available.

2.2.7.1.1.2 Sub-CU Motion Derivation

The second step is to split the current CU into sub-CUs and obtain the motion information of each sub-CU from the block corresponding to each sub-CU in the collocated picture.

If the corresponding block for a sub-CU is coded with inter mode, the motion information is utilized to derive the final motion information of current sub-CU by invoking the derivation process for collocated MVs which is not different with the process for conventional TMVP process. Basically, if the corresponding block is predicted from the target list X for uni-prediction or bi-prediction, the motion vector is utilized; otherwise, if it is predicted from list Y (Y=1−X) for uni or bi-prediction and NoBackwardPredFlag is equal to 1, MV for list Y is utilized. Otherwise, no motion candidate could be found.

If the block in the collocated picture identified by the initialized MV and location of current sub-CU is intra or IBC coded, or no motion candidate could be found as described aforementioned, the following further apply:

Denote the motion vector used to fetch the motion field in the collocated picture R_(col) as MV_(col). To minimize the impact due to MV scaling, the MV in the spatial candidate list used to derive MV_(col) is selected in the following way: if the reference picture of a candidate MV is the collocated picture, this MV is selected and used as MV_(col) without any scaling. Otherwise, the MV having a reference picture closest to the collocated picture is selected to derive MV_(col) with scaling.

The related decoding process for collocated motion vectors derivation process in JVET-N1001 is described as follows, with the parts related to ATMVP highlighted in bolded, capitalized font:

8.5.2.12 Derivation Process for Collocated Motion Vectors

Inputs to this process are:

-   a variable currCb specifying the current coding block, -   a variable colCb specifying the collocated coding block inside the     collocated picture specified by ColPic, -   a luma location (xColCb, yColCb) specifying the top-left sample of     the collocated luma coding block specified by colCb relative to the     top-left luma sample of the collocated picture specified by ColPic, -   a reference index refIdxLX, with X being 0 or 1, -   a flag indicating a subblock temporal merging candidate sbFlag.

Outputs of this process are:

-   the motion vector prediction mvLXCol in 1/16 fractional-sample     accuracy, -   the availability flag availableFlagLXCol.

The variable currPic specifies the current picture.

The arrays predFlagL0Col[x][y], mvL0Col[x][y] and refIdxL0Col[x][y] are set equal to PredFlagL0[x][y], MvDmvrL0[x][y] and RefIdxL0[x][y], respectively, of the collocated picture specified by ColPic, and the arrays predFlagL1Col [x][y], mvL1Col[x][y] and refIdxL1Col[x][y] are set equal to PredFlagL1[x][y], MvDmvrL1[x][y] and RefIdxL1[x][y], respectively, of the collocated picture specified by ColPic.

The variables mvLXCol and availableFlagLXCol are derived as follows:

-   If colCb is coded in an intra or IBC prediction mode, both     components of mvLXCol are set equal to 0 and availableFlagLXCol is     set equal to 0. -   Otherwise, the motion vector mvCol, the reference index refIdxCol     and the reference list identifier listCol are derived as follows:     -   If sbFlag is equal to 0, availableFlagLXCol is set to 1 and the         following applies:         -   If predFlagL0Col[xColCb][yColCb] is equal to 0, mvCol,             refIdxCol and listCol are set equal to             mvL1Col[xColCb][yColCb], refIdxL1 Col[xColCb][yColCb] and             L1, respectively.         -   Otherwise, if predFlagL0Col[xColCb][yColCb] is equal to 1             and predFlagL1Col[xColCb][yColCb] is equal to 0, mvCol,             refIdxCol and listCol are set equal to             mvL0Col[xColCb][yColCb], refIdxL0Col[xColCb][yColCb] and L0,             respectively.         -   Otherwise (predFlagL0Col[xColCb][yColCb] is equal to 1 and             predFlaglL1Col[xColCb][yColCb] is equal to 1), the following             assignments are made:             -   If NoBackwardPredFlag is equal to 1, mvCol, refIdxCol                 and listCol are set equal to mvLXCol[xColCb][yColCb],                 refIdxLXCol[xColCb][yColCb] and LX, respectively.             -   Otherwise, mvCol, refIdxCol and listCol are set equal to                 mvLNCol[xColCb][yColCb], refIdxLNCol[xColCb][yColCb] and                 LN, respectively, with N being the value of                 collocated_from_l0_flag.     -   OTHERWISE (SBFLAG IS EQUAL TO 1), THE FOLLOWING APPLIES:         -   IF PREDFLAGLXCOL[XCOLCB ][YCOLCB] IS EQUAL TO 1, MVCOL,             REFIDXCOL, AND LISTCOL ARE SET EQUAL TO             MVLXCOL[XCOLCB][YCOLCB], REFIDXLXCOL[XCOLCB][YCOLCB], AND             LX, RESPECTIVELY, AVAILABLEFLAGLXCOL IS SET TO 1.         -   OTHERWISE (PREDFLAGLXCOL[XCOLCB][YCOLCB] IS EQUAL TO 0), THE             FOLLOWING APPLIES:             -   IF DIFFPICORDERCNT(APIC, CURRPIC) IS LESS THAN OR EQUAL                 TO 0 FOR EVERY PICTURE APIC IN EVERY REFERENCE PICTURE                 LIST OF THE CURRENT SLICE AND                 PREDFLAGLYCOL[XCOLCB][YCOLCB] IS EQUAL TO 1, MVCOL,                 REFIDXCOL, AND LISTCOL ARE SET TO                 MVLYCOL[XCOLCB][YCOLCB], REFIDXLYCOL[XCOLCB][YCOLCB] AND                 LY, RESPECTIVELY, WITH Y BEING EQUAL TO !X WHERE X BEING                 THE VALUE OF X THIS PROCESS IS INVOKED FOR.                 AVAILABLEFLAGLXCOL IS SET TO 1.             -   BOTH THE COMPONENTS OF MVLXCOL ARE SET TO 0 AND                 AVAILABLEFLAGLXCOL IS SET EQUAL TO 0.     -   When availableFlagLXCol is equal to TRUE, mvLXCol and         availableFlagLXCol are derived as follows:         -   If LongTermRefPic(currPic, currCb, refIdxLX, LX) is not             equal to LongTermRefPic(ColPic, colCb, refIdxCol, listCol),             both components of mvLXCol are set equal to 0 and             availableFlagLXCol is set equal to 0.         -   Otherwise, the variable availableFlagLXCol is set equal to             1, refPicList[listCol] [refIdxCol] is set to be the picture             with reference index refIdxCol in the reference picture list             listCol of the slice containing coding block colCb in the             collocated picture specified by ColPic, and the following             applies:

colPocDiff=DiffPicOrderCnt(ColPic, refPicList[listCol][refIdxCol])  (8-402)

currPocDiff=DiffPicOrderCnt(currPic, RefPicList[X][refIdxLX])  (8-403)

-   -   -   -   The temporal motion buffer compression process for                 collocated motion vectors as specified in clause                 8.5.2.15 is invoked with mvCol as input, and the                 modified mvCol as output.             -   If RefPicList[X][refIdxLX] is a long-term reference                 picture, or colPocDiff is equal to currPocDiff, mvLXCol                 is derived as follows:

mvLXCol=mvCol  (8-404)

-   -   -   -   Otherwise, mvLXCo1 is derived as a scaled version of the                 motion vector mvCol as follows:

tx=(16384+(Abs(td)>>1))/td  (8-405)

distScaleFactor=Clip3)−4096, 4095, (tb*tx+32)>>6)  (8-406)

mvLXCol=Clip3(−131072, 131071, (distScaleFactor*mvCol+128−(distScaleFactor*mvCol>=0))>>8))  (8-407)

-   -   -   -    where td and tb are derived as follows:

td=Clip3(−128, 127, colPocDiff)  (8-408)

tb=Clip3(−128, 127, currPocDiff)  (8-409)

2.2.8 Regular Inter Mode (AMVP) 2.2.8.1 AMVP Motion Candidate List

Similar to the AMVP design in HEVC, up to 2 AMVP candidates may be derived. However, the HMVP candidates may also be added after the TMVP candidate. The HMVP candidates in the HMVP table are traversed in an ascending order of index (i.e., from index equal to 0, the oldest one). Up to 4 HMVP candidates may be checked to find whether its reference picture is the same as the target reference picture (i.e., same POC value).

2.2.8.2 AMVR

In HEVC, motion vector differences (MVDs) (between the motion vector and predicted motion vector of a PU) are signalled in units of quarter luma samples when use_integer_mv_flag is equal to 0 in the slice header. In the VVC, a locally adaptive motion vector resolution (AMVR) is introduced. In the VVC, MVD can be coded in units of quarter luma samples, integer luma samples or four luma samples (i.e., ¼-pel, 1-pel, 4-pel). The MVD resolution is controlled at the coding unit (CU) level, and MVD resolution flags are conditionally signalled for each CU that has at least one non-zero MVD components.

For a CU that has at least one non-zero MVD components, a first flag is signalled to indicate whether quarter luma sample MV precision is used in the CU. When the first flag (equal to 1) indicates that quarter luma sample MV precision is not used, another flag is signalled to indicate whether integer luma sample MV precision or four luma sample MV precision is used.

When the first MVD resolution flag of a CU is zero, or not coded for a CU (meaning all MVDs in the CU are zero), the quarter luma sample MV resolution is used for the CU. When a CU uses integer-luma sample MV precision or four-luma-sample MV precision, the MVPs in the AMVP candidate list for the CU are rounded to the corresponding precision.

2.2.8.3 Symmetric Motion Vector Difference in JVET-N1001-v2

In JVET-N1001-v2, symmetric motion vector difference (SMVD) is applied for motion information coding in bi-prediction.

Firstly, in slice level, variables RefIdxSymL0 and RefIdxSymL1 to indicate the reference picture index of list 0/1 used in SMVD mode, respectively, are derived with the following steps as specified in N1001-v2. When at least one of the two variables are equal to −1, SMVD mode shall be disabled.

2.2.9 Refinement of Motion Information 2.2.9.1 Decoder-Side Motion Vector Refinement (DMVR)

In bi-prediction operation, for the prediction of one block region, two prediction blocks, formed using a motion vector (MV) of list0 and a MV of list1, respectively, are combined to form a single prediction signal. In the decoder-side motion vector refinement (DMVR) method, the two motion vectors of the bi-prediction are further refined.

For DMVR in VVC, MVD mirroring between list 0 and list 1 is assumed as shown in FIG. 19 and bilateral matching is performed to refine the MVs, i.e., to find the best MVD among several MVD candidates. Denote the MVs for two reference picture lists by MVL0(L0X, L0Y), and MVL1(L1X, L1Y). The MVD denoted by (MvdX, MvdY) for list 0 that could minimize the cost function (e.g., SAD) is defined as the best MVD. For the SAD function, it is defined as the SAD between the reference block of list 0 derived with a motion vector (L0X+MvdX, L0Y+MvdY) in the list 0 reference picture and the reference block of list 1 derived with a motion vector (L1X-MvdX, L1Y-MvdY) in the list 1 reference picture.

The motion vector refinement process may iterate twice. In each iteration, at most 6 MVDs (with integer-pel precision) may be checked in two steps, as shown in FIG. 20. In the first step, MVD (0, 0), (−1, 0), (1, 0), (0, −1), (0, 1) are checked. In the second step, one of the MVD (−1, −1), (−1, 1), (1, −1) or (1, 1) may be selected and further checked. Suppose function Sad(x, y) returns SAD value of the MVD (x, y). The MVD, denoted by (MvdX, MvdY), checked in the second step is decided as follows:

MvdX=−1;

MvdY=−1;

If (Sad(1, 0)<Sad(−1, 0)) MvdX=1;

If (Sad(0, 1)<Sad(0, −1)) MvdY=1;

In the first iteration, the starting point is the signaled MV, and in the second iteration, the starting point is the signaled MV plus the selected best MVD in the first iteration. DMVR applies only when one reference picture is a preceding picture and the other reference picture is a following picture, and the two reference pictures are with same picture order count distance from the current picture.

To further simplify the process of DMVR, JVET-M0147 proposed several changes to the design in JEM. More specifically, the adopted DMVR design to VTM-4.0 (to be released soon) has the following main features:

-   -   Early termination when (0,0) position SAD between list0 and         list1 is smaller than a threshold.     -   Early termination when SAD between list0 and list1 is zero for         some position.     -   Block sizes for DMVR: W*H>=64 && H>=8, wherein W and H are the         width and height of the block.     -   Split the CU into multiple of 16×16 sub-blocks for DMVR of CU         size >16*16. If only width or height of the CU is larger than         16, it is only split in vertical or horizontal direction.     -   Reference block size (W+7)*(H+7) (for luma).     -   25 points SAD-based integer-pel search (i.e. (+−) 2 refinement         search range, single stage)     -   Bilinear-interpolation based DMVR.     -   “Parametric error surface equation” based sub-pel refinement.         This procedure is performed only when the minimum SAD cost is         not equal to zero and the best MVD is (0, 0) in the last MV         refinement iteration.     -   Luma/chroma MC w/reference block padding (if needed).     -   Refined MVs used for MC and TMVPs only.

2.2.9.1.1 Usage of DMVR

When the following conditions are all true, DMVR may be enabled:

-   -   DMVR enabling flag in the SPS (i.e., sps_dmvr_enabled_flag) is         equal to 1     -   TPM flag, inter-affine flag and subblock merge flag (either         ATMVP or affine merge), MMVD flag are all equal to 0     -   Merge flag is equal to 1     -   Current block is bi-predicted, and POC distance between current         picture and reference picture in list 1 is equal to the POC         distance between reference picture in list 0 and current picture     -   The current CU height is greater than or equal to 8     -   Number of luma samples (CU width*height) is greater than or         equal to 64

2.2.9.1.2 “Parametric Error Surface Equation” Based Sub-Pel Refinement

The method is summarized below:

-   -   1. The parametric error surface fit is computed only if the         center position is the best cost position in a given iteration.     -   2. The center position cost and the costs at (−1,0), (0,−1),         (1,0) and (0,1) positions from the center are used to fit a 2-D         parabolic error surface equation of the form

E(x, y)=A(x−x ₀)² +B(y−y ₀)² +C

-   -    where (x₀,y₀) corresponds to the position with the least cost         and C corresponds to the minimum cost value. By solving the 5         equations in 5 unknowns, (x₀,y₀) is computed as:

x ₀=(E(−1,0)−E(1,0))/(2(E)−1,0)+E(1,0)−2E(0,0)))

y ₀=(E(0,−1)−E(0,1))/(2((E(0,−1)+E(0,1)−2E(0,0)))

-   -    (x₀,y₀) can be computed to any required sub-pixel precision by         adjusting the precision at which the division is performed (i.e.         how many bits of quotient are computed). For 1/16-pel accuracy,         just 4-bits in the absolute value of the quotient needs to be         computed, which lends itself to a fast-shifted subtraction-based         implementation of the 2 divisions required per CU.     -   3. The computed (x₀, y₀) are added to the integer distance         refinement MV to get the sub-pixel accurate refinement delta MV.

2.3 Intra Block Copy

Intra block copy (IBC), a.k.a. current picture referencing, has been adopted in HEVC Screen Content Coding extensions (HEVC-SCC) and the current VVC test model (VTM-4.0). IBC extends the concept of motion compensation from inter-frame coding to intra-frame coding. As demonstrated in FIG. 21. the current block is predicted by a reference block in the same picture when IBC is applied. The samples in the reference block must have been already reconstructed before the current block is coded or decoded. Although IBC is not so efficient for most camera-captured sequences, it shows significant coding gains for screen content. The reason is that there are lots of repeating patterns, such as icons and text characters in a screen content picture. IBC can remove the redundancy between these repeating patterns effectively. In HEVC-SCC, an inter-coded coding unit (CU) can apply IBC if it chooses the current picture as its reference picture. The MV is renamed as block vector (BV) in this case, and a BV always has an integer-pixel precision. To be compatible with main profile HEVC, the current picture is marked as a “long-term” reference picture in the Decoded Picture Buffer (DPB). It should be noted that similarly, in multiple view/3D video coding standards, the inter-view reference picture is also marked as a “long-term” reference picture.

Following a BV to find its reference block, the prediction can be generated by copying the reference block. The residual can be got by subtracting the reference pixels from the original signals. Then transform and quantization can be applied as in other coding modes.

However, when a reference block is outside of the picture, or overlaps with the current block, or outside of the reconstructed area, or outside of the valid area restricted by some constrains, part or all pixel values are not defined. Basically, there are two solutions to handle such a problem. One is to disallow such a situation, e.g. in bitstream conformance. The other is to apply padding for those undefined pixel values. The following sub-sessions describe the solutions in detail.

2.3.1 IBC in VVC Test Model (VTM4.0)

In the current VVC test model, i.e. VTM-4. 0 design, the whole reference block should be with the current coding tree unit (CTU) and does not overlap with the current block. Thus, there is no need to pad the reference or prediction block. The IBC flag is coded as a prediction mode of the current CU. Thus, there are totally three prediction modes, MODE_INTRA, MODE_INTER and MODE_IBC for each CU.

2.3.1.1 IBC Merge Mode

In IBC merge mode, an index pointing to an entry in the IBC merge candidates list is parsed from the bitstream. The construction of the IBC merge list can be summarized according to the following sequence of steps:

-   -   Step 1: Derivation of spatial candidates     -   Step 2: Insertion of HMVP candidates     -   Step 3: Insertion of pairwise average candidates

In the derivation of spatial merge candidates, a maximum of four merge candidates are selected among candidates located in the positions depicted in A₁, B₁, B₀, A₀ and B₂ as depicted in FIG. 2. The order of derivation is A₁, B₁, B₀, A₀ and B₂. Position B₂ is considered only when any PU of position A₁, B₁, B₀, A₀ is not available (e.g. because it belongs to another slice or tile) or is not coded with IBC mode. After candidate at position A₁ is added, the insertion of the remaining candidates is subject to a redundancy check which ensures that candidates with same motion information are excluded from the list so that coding efficiency is improved.

After insertion of the spatial candidates, if the IBC merge list size is still smaller than the maximum IBC merge list size, IBC candidates from HMVP table may be inserted. Redundancy check are performed when inserting the HMVP candidates.

Finally, pairwise average candidates are inserted into the IBC merge list.

When a reference block identified by a merge candidate is outside of the picture, or overlaps with the current block, or outside of the reconstructed area, or outside of the valid area restricted by some constrains, the merge candidate is called invalid merge candidate.

It is noted that invalid merge candidates may be inserted into the IBC merge list.

2.3.1.2 IBC AMVP Mode

In IBC AMVP mode, an AMVP index point to an entry in the IBC AMVP list is parsed from the bitstream. The construction of the IBC AMVP list can be summarized according to the following sequence of steps:

-   -   Step 1: Derivation of spatial candidates         -   Check A₀, A₁ until an available candidate is found.         -   Check B₀, B₁, B₂ until an available candidate is found.     -   Step 2: Insertion of HMVP candidates     -   Step 3: Insertion of zero candidates

After insertion of the spatial candidates, if the IBC AMVP list size is still smaller than the maximum IBC AMVP list size, IBC candidates from HMVP table may be inserted.

Finally, zero candidates are inserted into the IBC AMVP list.

2.3.1.3 Chroma IBC Mode

In the current VVC, the motion compensation in the chroma IBC mode is performed at sub block level. The chroma block will be partitioned into several sub blocks. Each sub block determines whether the corresponding luma block has a block vector and the validity if it is present. There is encoder constrain in the current VTM, where the chroma IBC mode will be tested if all sub blocks in the current chroma CU have valid luma block vectors. For example, on a YUV 420 video, the chroma block is N×M and then the collocated luma region is 2N×2M. The sub block size of a chroma block is 2×2. There are several steps to perform the chroma my derivation then the block copy process.

-   -   1) The chroma block will be first partitioned into (N>>1)*(M>>1)         sub blocks.     -   2) Each sub block with a top left sample coordinated at (x, y)         fetches the corresponding luma block covering the same top-left         sample which is coordinated at (2x, 2y).     -   3) The encoder checks the block vector (bv) of the fetched luma         block. If one of the following conditions is satisfied, the by         is considered as invalid.         -   a. A bv of the corresponding luma block is not existing.         -   b. The prediction block identified by a by is not             reconstructed yet.         -   c. The prediction block identified by a by is partially or             fully overlapped with the current block.     -   4) The chroma motion vector of a sub block is set to the motion         vector of the corresponding luma sub block.

The IBC mode is allowed at the encoder when all sub blocks find a valid by.

2.3.2 Single BV List for IBC (in VTM5.0)

JVET-N0843 is adopted to the VVC. In the JVET-N0843, the BV predictors for merge mode and AMVP mode in IBC will share a common predictor list, which consist of the following elements:

-   -   2 spatial neighboring positions (A1, B1 as in FIG. 2)     -   5 HMVP entries     -   Zero vectors by default

The number of candidates in the list is controlled by a variable derived from the slice header. For merge mode, up to first 6 entries of this list will be used; for AMVP mode, the first 2 entries of this list will be used. And the list conforms with the shared merge list region requirement (shared the same list within the SMR).

In addition to the above-mentioned BV predictor candidate list, JVET-N0843 also proposed to simplify the pruning operations between HMVP candidates and the existing merge candidates (A1, B1). In the simplification there will be up to 2 pruning operations since it only compares the first HMVP candidate with spatial merge candidate(s).

3. Problems

The current design of merge modes may have the following problems:

-   -   1. The regular merge list construction process depends on the         usage of TPM for the current block.         -   a. For TPM-coded blocks, full pruning is applied among             spatial merge candidates.         -   b. For non-TPM-coded blocks, partial pruning is applied             among spatial merge candidates.     -   2. According to current design, all merge related tools         (including IBC merge, regular merge, MMVD, sub-block merge,         CIIP, TPM) are signalled by one flag, named general_merge_flag         However, it is possible that when this flag is true, all merge         related tools are signaled or to be derived to be disabled. How         to handle this case is unknown. In addition, it is disallowed to         tum off the merge mode, that is the maximum number of merge         candidate shall be unequal to 0. However, for high throughput         encoder/decoder, it may need to force disabling the merge mode.     -   3. The decision of initialized MV for ATMVP process is dependent         on slice type, all reference pictures' POC values,         collocated_from_l0_flag, etc. al, which delays the throughput of         MVs.     -   4. Derivation process of collocated MVs is dependent on the         usage of sub-block technology, such as the conventional TMVP         process or ATMVP process which requires additional logic.     -   5. For a sub-CU in ATMVP coded block, even its corresponding         collocated block is inter coded, it is possible the sub-CU's         motion information couldn't be derived from the corresponding         collocated block, but filled with other motion information. Such         design is sub-optimal for both coding efficiency and throughput.     -   6. The HEVC specification defines the availability of one         neighbouring block in current or reference picture based on         whether the block is constructed or in a different CTU row/slice         etc. al. However, in VVC, multiple coding methods have been         introduced. Different definitions of a block's availability may         need to be defined.     -   7. JVET-O0545 proposes to signal the indication of maximum         transform block size by sending sps_sbt_max_size_64_flag.         -   sps_sbt_max_size_64_flag equal to 0 specifies that the             maximum CU width and height for allowing subblock transform             is 32 luma samples. sps_sbt_max_size_64_flag equal to 1             specifies that the maximum CU width and height for allowing             subblock transform is 64 luma samples.

MaxSbtSize=sps_sbt_max_size-64_flag ? 64:32  (7 31)

-   -   -   To support maximum transform size (indicated by             MaxTransformSize) smaller than 64, the derivation of             MaxSbtSize is modified as below,

MaxSbtSize=min(MaxTransformSize, sps_sbt_max_size_64_flag ? 64 : 32)

-   -   8. Adaptive loop filter (ALF) coefficients are restricted to be         within a fixed range. For example: chroma ALF filter         coefficients, denoted by AlfCoeff_(C), and luma ALF filter         coefficients, denoted by AlfCoeff_(L), shall be in the range of         −2⁷ to 2⁷−1, inclusive. Such restriction is based on the         assumption of 8-bit depth.     -   9. Indication of predictors of ALF filters is signalled as         follows:

if( slice _alf_enabled_flag){  alf_ctb_flag[ 0 ][ xCtb >> Log2CtbSize ][ yCtb >> ae(v) Log2CtbSize ]  if( alf_ctb_flag[ 0 ][ xCtb >> Log2Ctb Size ][ yCtb >> Log2CtbSize ]) {   if( slice_num_alf_aps_ids_luma > 0)    alf_ctb_use_first_aps_flag ae(v)   if( !alf_ctb_use_first_aps_flag ) {    if( slice_num_alf_aps_ids_luma > 1)     alf_use_aps_flag ae(v)    if( alf_use_aps_flag )     if( slice_num_alf_aps_ids_luma > 2 )      alf_luma_prev_filter_idx_minus1 ae(v)    else     alf_luma_fixed_filter_idx ae(v)   }  }

-   -    It can be seen that such a method needs to parse multiple         syntax elements to determine to use filters from which APS sets         or from fixed filters.     -   10. Merge related coding tools are as follows:

Descriptor merge_data( x0, y0, cbWidth, cbHeight) {  if ( CuPredMode[ x0 ][ y0 ] == MODE_IBC ) {   if( MaxNumMergeCand> 1)    merge_idx[ x0 ][ y0 ] ae(v)  } else {   if( MaxNumSubblockMergeCand> 0 && cbWidth >=8 && cbHeight >=8 )    merge_subblock_flag[ x0 ][ y0 ] ae(v)   if( merge_subblock_flag[ x0 ][ y0 ] == 1) {    if( MaxNumSubblockMergeCand> 1)      merge_subblock_idx[ x0 ][ y0 ] ae(v)    } else {   if( ( cbWidth * cbHeight) >= 64 && ((sps_ciip_enabled_flag&& cu_skip_flag[ x0 ][ y0 ] == 0 && cbWidth < 128 && cbHeight < 128) || ( sps_triangle_enabled_flag&& slice_type == B) ) {   regular_merge_flag[ x0 ][ y0 ] ae(v)   }   if( regular_merge_flag[ x0 ][ y0 ]) {    if( sps_mmvd_enabled_flag)    {    mmvd_merge_flag[ x0 ][ y0 ] ae(v)     if(mmvd_merge_flag[ x0 ][ y0 ] == 1 ) {      if( MaxNumMergeCand> 1)      mmvd_cand_flag[ x0 ][ y0 ] ae(v)     mmvd_distance_idx[ x0 ][ y0 ] ae(v)     mmvd_direction_idx[ x0 ][ y0 ] ae(v)    } else {     if( MaxNumMergeCand > 1 )      merge_idx[ x0 ][ y0 ] ae(v)     }    }   } else {    if(sps_ciip_enabled_flag&& cu_skip_flag[ x0 ][ y0 ] == 0 && cbWidth < 128 && cbHeight < 128 && sps_triangle_enabled_flag&& slice_type == B) {    ciip_flag[ x0 ][ y0 ] ae(v)     if( ciip_flag[ x0 ][ y0 ] && MaxNumMergeCand > 1 )      merge_idx[ x0 ][ y0 ] ae(v)     }     if( ! ciip_flag[ x0 ][ y0 ]) {      merge_triangle_split_dir[ x0 ][ y0 ] ae(v)      merge_triangle_idx0[ x0 ][ y0 ] ae(v)      merge_triangle_idx1[ x0 ][ y0 ] ae(v)     }   }   }  }  } }

It is noted that the sub-block merge related syntax elements are firstly signalled; followed by the indication of regular merge mode (which controls both MMVP and conventional merge like in HEVC). When such indication is false, additional bits may be further signalled to indicate whether it is CIIP or TPM mode.

However, such information doesn't take into consideration of the case that number of allowed TPM candidates is less than 2.

4. Examples of Techniques and Embodiments

The detailed listing below should be considered as examples to explain general concepts. These embodiments should not be interpreted in a narrow way. Furthermore, these techniques can be combined in any manner.

The neighbouring blocks denoted as A0, A1, B0, B1, B2 etc. are shown in FIG. 2.

-   -   1. The regular merge list construction process for conventional         merge and TPM coded blocks is decoupled from the coding method         of the current block.         -   a. In one example, partial pruning is applied to spatial             merge candidates when TPM is applied to one block.             -   i. In one example, whether two candidates are compared                 with each other are determined in the same way as that                 used for a non-TPM merge coded blocks.             -   ii. In one example, B1 is compared to A1, B0 is compared                 to B1, A0 is compared to A1, B2 is compared to B1 and                 A1.             -   iii. Alternatively, full pruning is applied to spatial                 merge candidates even TPM is not used for one block.             -   iv. Alternatively, furthermore, full pruning may be                 applied to some specific block dimensions.                 -   1. For example, full pruning may be applied to block                     dimensions wherein TPM is allowed.                 -   2. For example, when a block size contains less than                     M*H samples, e.g., 16 or 32 or 64 luma samples, full                     pruning is not allowed.                 -   3. For example, when a block's width>th1 or >=th1                     and/or a block's height>th2 or >=th2, full pruning                     is not allowed.         -   b. In one example, whether to check B2 is based on the             number of available merge candidates before checking B2 when             TPM is applied to one block.             -   i. Alternatively, B2 is always checked regardless the                 number of available merge candidates for non-TPM merge                 coded blocks.     -   2. The initialized MV used for identifying a block to determine         whether ATMVP is available or not may just rely on the list X         information of a spatial neighbouring block (e.g., A1), and Xis         set to where the collocated picture used for temporal motion         vector prediction is derived from (e.g.,         collocated_from_l0_flag).         -   a. Alternatively, X is decided according to whether all             reference pictures in all reference lists are with smaller             POC values or no greater POC values compared to the current             picture.             -   i. In on example, if it is true, Xis set to 1.                 Otherwise, Xis set to 0.         -   b. Alternatively, if the reference picture associated with             list X of a spatial neighbouring block (e.g., A1) is             available and has the same POC value as the col-located             picture, the initialized MV is set to the MV associated with             list X of the spatial neighbouring block Otherwise, a             default MV (e.g., (0, 0)) is utilized.         -   c. Alternatively, motion information stored in HMVP table             may be used as the initialized MV in ATMVP.             -   i. For example, the first available motion information                 stored in HMVP table may be used.             -   ii. For example, the first available motion information                 stored in HMVP table that is associated with certain                 reference picture (e. g., collocated picture) may be                 used.         -   d. Alternatively, X is a fixed number, such as 0 or 1.     -   3. The derivation process of collocated MVs used for sub-block         based coding tools and non-sub-block based coding tools may be         aligned, i.e., the process is independent from the usage of a         certain coding tool.         -   a. In one example, the whole or partial of the derivation             process of collocated MVs for sub-block based coding tools             is aligned to that used for TMVP.             -   i. In one example, if it is uni-prediction from list Y,                 the motion vector of list Y is scaled to a target                 reference picture list X;             -   ii. In one example, if it is bi-prediction and the                 target reference picture list is X, the motion vector of                 list Y is scaled to the target reference picture list X,                 and Y may be determined according to the following                 rules:                 -   If none of reference pictures has a greater POC                     values or all reference pictures have smaller POC                     values compared to current picture, Y is set equal                     to X.                 -   Otherwise, Y is set equal to                     collocated_from_l0_flag.         -   b. In one example, the whole or partial of the derivation             process of collocated MVs for TMVP is aligned to that used             for sub-block-based coding tools.     -   4. The motion candidate list construction process (e.g., regular         merge list, IBC merge/AMVP list) may depend on the block         dimensions and/or merge sharing conditions. Denote a block's         width and height as W and H, respectively. Condition C may         depend on W and H and/or merge sharing conditions.         -   a. In one example, derivation of spatial merge candidates is             skipped if condition C is satisfied.         -   b. In one example, derivation of HMVP candidates is skipped             if condition C is satisfied.         -   c. In one example, derivation of pairwise merge candidates             is skipped if condition C is satisfied.         -   d. In one example, number of maximum pruning operations is             reduced or set to 0 if condition C is satisfied.         -   e. In one example, condition C is satisfied when W*H is             smaller or no larger than a threshold (e.g., 64 or 32).         -   f. In one example, condition C is satisfied when W and/or H             is smaller or no larger than a threshold (e.g., 4 or 8).         -   g. In one example, condition C is satisfied when the current             block is under a shared node.     -   5. The maximum number of allowed regular merge         candidates/maximum number of allowed IBC candidates/maximum         number of allowed sub-block merge candidates may be set to 0.         Therefore, certain tools may be disabled, and related syntax         elements are not needed to be signalled.         -   a. In one example, when the maximum number of allowed             regular merge candidates is equal to 0, a coding tool which             relies on regular merge list may be disabled. The coding             tool may be regular merge, MMVD, CIIP, TPM, DMVR etc. al.         -   b. In one example, when the maximum number of allowed IBC             candidates is equal to 0, IBC AMVP and/or IBC merge may be             disabled.         -   c. In one example, when the maximum number of allowed             sub-block based merge candidates is equal to 0, sub-block             based technologies, e.g., ATMVP, affine merge mode may be             disabled.         -   d. When a tool is disabled according to the maximum number             of allowed candidates, signaling of related syntax elements             is skipped.             -   i. Alternatively, furthermore, the signalling of merge                 related tools may need to check whether the maximum                 number of allowed candidates is unequal to 0.             -   ii. Alternatively, furthermore, invoking of a process                 for the merge related tools may need to check whether                 the maximum number of allowed candidates is unequal to                 0.     -   6. The signalling of general_merge_flag and/or cu_skip_flag may         depend on the maximum number of allowed regular merge         candidates/maximum number of allowed IBC candidates/maximum         number of allowed sub-block merge candidates/usage of merge         related coding tools.         -   a. In one example, merge related coding tools may include             IBC merge, regular merge, MMVD, sub-block merge, CIIP, TPM,             DMVR and etc.         -   b. In one example, when the maximum number of allowed             regular merge candidates, the maximum number of allowed IBC             merge/AMVP candidates, the maximum number of allowed             sub-block merge candidate are equal to 0, the             general_merge_flag and/or cu_skip_flag is not signaled.             -   i. Alternatively, furthermore, general_merge_flag and/or                 cu_skip_flag is inferred to be 0.     -   7. A conformance bitstream shall satisfy that at least one of         the merge related tools including IBC merge, regular merge,         MMVD, sub-block merge, CIIP, TPM, DMVR and etc. is enabled when         the general_merge_flag or cu_skip_flag of the current block is         true.     -   8. A conformance bitstream shall satisfy that at least one of         the merge related tools including regular merge, MMVD, sub-block         merge, CIIP, TPM, DMVR and etc. is enabled when the         (general_merge_flag or cu_skip_flag) of the current block is         true and IBC is disabled for one         slice/tile/brick/picture/current block.     -   9. A conformance bitstream shall satisfy that at least one of         the merge related tools including IBC merge, regular merge,         sub-block merge, CIIP, TPM is enabled when the         (general_merge_flag or cu_skip_flag) of the current block is         true and MMVD is disabled for one         slice/tile/brick/picture/current block.     -   10. A conformance bitstream shall satisfy that at least one of         the merge related tools including IBC merge, regular merge,         MMVD, sub-block merge, TPM is enabled when the         (general_merge_flag or cu_skip_flag) of the current block is         true and CIIP is disabled for one         slice/tile/brick/picture/current block.     -   11. A conformance bitstream shall satisfy that at least one of         the merge related tools including IBC merge, regular merge,         MMVD, sub-block merge, CIIP is enabled when the         (general_merge_flag or cu_skip_flag) of the current block is         true and TPM is disabled for one         slice/tile/brick/picture/current block.     -   12. A conformance bitstream shall satisfy that at least one of         the enabled merge related tools including IBC merge, regular         merge, MMVD, sub-block merge, CIIP, TPM is applied when the         general_merge_flag or cu_skip_flag of the current block is true.         When coding a first block, the check of availability of a 2^(nd)         block may depend on the coded mode information of the first         block, for example, if different modes are used in the 1^(st)         and 2^(nd) block, the 2^(nd) block may be treated as unavailable         even regardless of other condition checking results (e.g., has         been constructed).         -   a. In one example, when 1^(st) block is inter coded and             2^(nd) block is IBC code, 2^(nd) block is marked as             unavailable.         -   b. In one example, when 1^(st) block is IBC coded and 2^(nd)             block is inter code, 2^(nd) block is marked as unavailable.         -   c. When the 2^(nd) is marked as unavailable, the related             coded information (e.g., motion information) is disallowed             to be utilized for coding the 1^(st) block.     -   13. The signalling of syntax elements irrelated to TPM side         information may be also under the condition check of number of         allowed TPM candidates.         -   a. In one example, the signalling of CIIP related syntax             elements (e.g., ciip_flag) may dependent on number of             allowed TPM candidate is greater than a threshold K.         -   b. In one example, the signalling of regular merge mode flag             (e.g., regular_merge_flag) may dependent on number of             allowed TPM candidate is greater than a threshold K.         -   c. In one example, K is set to 1.         -   d. Alternatively, furthermore, certain syntax elements may             be not signalled when the number of allowed TPM candidate is             no greater than a threshold K.     -   14. A conformance bitstream shall satisfy that the maximum         transform block sizes shall not exceed the maximum CTU sizes.         -   a. Alternatively, when the indication of maximum transform             block size may be conditionally signalled under the maximum             CTU sizes or vice versa.             -   i. In one example, if the maximum CTU size is no greater                 than or equal to M×N (e.g., M=N=32), there is no need to                 signal the indication of maximum transform block size.     -   15. The ALF filter coefficients range may be dependent on the         sample depth (e.g., internal bit-depth or input bit-depth)         instead of being in a fixed range.     -   16. One flag may be directly signalled to indicate whether to         use ALF filters in ALF APS to fixed filters.         -   a. In addition, such a flag may be signalled under the             condition that number of available ALF APS is greater than             0.         -   b. Alternatively, furthermore, when ALF filters from APS is             signalled, one additional syntax may be further signalled to             indicate the index of ALF APS. Such an index may be coded             with Fixed-length coding, unary coding, truncated unary             coding, truncated binary coding, exp-golomb coding.

5. Embodiment

The suggested changes on top of the latest VVC working draft (JVET-N1001 v7) are given as follows. The deleted text is marked with underlined italicized font. The newly added parts are highlighted in bolded capitalized font.

5.1 Embodiment #1

This embodiment is to align the pruning process for non-TPM coded block to that for TPM coded blocks i.e., full pruning operations for non-TPM coded blocks.

8.5.2.3 Derivation Process for Spatial Merging Candidates

Inputs to this process are:

-   a luma location (xCb, yCb) of the top-left sample of the current     luma coding block relative to the top-left luma sample of the     current picture, -   a variable cbWidth specifying the width of the current coding block     in luma samples, -   a variable cbHeight specifying the height of the current coding     block in luma samples.

Outputs of this process are as follows, with X being 0 or 1:

-   the availability flags availableFlagA₀, availableFlagA₁,     availableFlagB₀, availableFlagB₁ and availableFlagB₂ of the     neighbouring coding units, -   the reference indices refIdxLXA₀, refIdxLXA₁, refIdxLXB₀, refIdxLXB₁     and refIdxLXB₂ of the neighbouring coding units, -   the prediction list utilization flags predFlagLXA₀, predFlagLXA₁,     predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂ of the neighbouring     coding units, -   the motion vectors in 1/16 fractional-sample accuracy mvLXA₀,     mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂ of the neighbouring coding units, -   the bi-prediction weight indices gbiIdxAo, gbiIdxA₁, gbiIdxB₀,     gbiIdxB₁, and gbiIdxB₂.

For the derivation of availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁ the following applies:

-   The luma location (xNbA₁, yNbA₁) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbHeight−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₁, yNbA₁) as inputs, and the output is assigned to the block     availability flag availableA₁. -   The variables availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁     are derived as follows:     -   If availableA₁ is equal to FALSE, availableFlagA₁ is set equal         to 0, both components of mvLXA₁ are set equal to 0, refIdxLXA₁         is set equal to −1 and predFlagLXA₁ is set equal to 0, with X         being 0 or 1, and gbiIdxA₁ is set equal to 0.     -   Otherwise, availableFlagA₁ is set equal to 1 and the following         assignments are made:

mvLXA ₁=MvLX[xNbA ₁][yNbA ₁]  (8-294)

refIdxLXA ₁=RefIdxLX[xNbA ₁][yNbA ₁]  (8-295)

predFlagLXA ₁=PredFlagLX[xNbA ₁][yNbA ₁]  (8-296)

gbiIdxA ₁ =GbiIdx[xNbA ₁][yNbA ₁]  (8-297)

For the derivation of availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁ the following applies:

-   The luma location (xNbB₁, yNbB₁) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth−1, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₁, yNbB₁) as inputs, and the output is assigned to the block     availability flag availableB₁. -   The variables availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₁ is set equal to 0, both components of mvLXB₁ are         set equal to 0, refIdxLXB₁ is set equal to −1 and predFlagLXB₁         is set equal to 0, with X being 0 or 1, and gbiIdxB₁ is set         equal to 0:         -   availableB₁ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₁, yNbB₁) have the same motion vectors and             the same reference indices.     -   Otherwise, availableFlagB₁ is set equal to 1 and the following         assignments are made:

mvLXB ₁=MvLX[xNB ₁][yNbB ₁]  (8-298)

refIdxLXB ₁RefIdxLX[xNbB ₁][yNbB ₁]  (8-299)

predFlagLXB ₁=PredFlagLX[xNbB ₁][yNbB ₁]  (8-300)

gbiIdxB₁ =GbiIdx[xNbB ₁][yNbB ₁]  (8-301)

For the derivation of availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀ the following applies:

-   The luma location (xNbB₀, yNbB₀) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₀, yNbB₀) as inputs, and the output is assigned to the block     availability flag availableB₀. -   The variables availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₀ is set equal to 0, both components of mvLXB₀ are         set equal to 0, refIdxLXB₀is set equal to −1 and predFlagLXB₀ is         set equal to 0, with X being 0 or 1, and gbiIdxB₀ is set equal         to 0:         -   availableB₀ is equal to FALSE.         -   availableB₁ is equal to TRUE and the luma locations (xNbB₁,             yNbB₁) and(xNbB₀, yNbB₀) have the same motion vectors and             the same reference indices.         -   availableA₁ is equal to TRUE, the luma locations (xNbA₁,             yNbA₁) and (xNbB₀, yNbB₀) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.     -   Otherwise, availableFlagB₀ is set equal to 1 and the following         assignments are made:

mvLXB ₀=MvLX[xNbB ₀][yNbB ₀]  (8-302)

refIdxLXB ₀=RefIdxLX[xNbB ₀][yNbB ₀]  (8-303)

predFlagLXB ₀=PredFlagLX[xNbB ₀][yNbB ₀]  (8-304)

gbiIdxB ₀ ==GbiIdx[xNbB ₀][yNbB ₀]  (8-305)

For the derivation of availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀ the following applies:

-   The luma location (xNbA₀, yNbA₀) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbWidth). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₀, yNbA₀) as inputs, and the output is assigned to the block     availability flag availableA₀. -   The variables availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagA₀ is set equal to 0, both components of mvLXA₀ are         set equal to 0, refIdxLXA₀ is set equal to −1 and predFlagLXA₀         is set equal to 0, with X being 0 or 1, and gbiIdxAo is set         equal to 0:         -   availableA₀ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE, the luma locations (xNbB₁,             yNbB₁) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.     -   Otherwise, availableFlagA₀ is set equal to 1 and the following         assignments are made:

mvLXA ₀=MvLX[xNbA ₀][yNbA ₀]  (8-306)

refIdxLXA ₀=RefIdxLX[xNbA ₀][yNbA ₀]  (8-307)

predFlagLXA ₀=PredFlagLX[xNbA ₀][yNbA ₀]  (8-308)

gbiIdxA ₀ =GbiIdx[xNbA ₀][yNbA ₀]  (8-309)

For the derivation of availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂ the following applies:

-   The luma location (xNbB₂, yNbB₂) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₂, yNbB₂) as inputs, and the output is assigned to the block     availability flag availableB₂. -   The variables availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₂ is set equal to 0, both components of mvLXB₂ are         set equal to 0, refIdxLXB₂ is set equal to −1 and predFlagLXB₂         is set equal to 0, with X being 0 or 1, and gbiIdxB₂ is set         equal to 0:         -   availableB₂ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE and the luma locations (xNbB₁,             yNbB₁) and(xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.         -   availableA₀ is equal to TRUE, the luma locations (xNbA₀,             yNbA₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.         -   availableFlagA₀+availableFlagA₁+availableFlagB₀+availableFlagB₁             is equal to 4 and merge_triangle_flag[xCb][yCb] is equal to             0.     -   Otherwise, availableFlagB₂ is set equal to 1 and the following         assignments are made:

mvLXB ₂=MvLX[xNbB ₂][yNbB ₂]  (8-310)

refIdxLXB ₂=RefIdxLX[xNbB ₂][yNbB ₂]  (8-311)

predFlagLXB ₂=PredFlagLX[xNbB ₂][yNbB ₂]  (8-312)

gbiIdxB ₂ =GbiIdx[xNbB ₂][yNbB ₂]  (8-313)

5.2 Embodiment #2

This embodiment is to align the pruning process for TPM coded block to that for non-TPM coded blocks, i.e., limited pruning operations for TPM coded blocks.

8.5.2.3 Derivation Process for Spatial Merging Candidates

Inputs to this process are:

-   a luma location (xCb, yCb) of the top-left sample of the current     luma coding block relative to the top-left luma sample of the     current picture, -   a variable cbWidth specifying the width of the current coding block     in luma samples, -   a variable cbHeight specifying the height of the current coding     block in luma samples.

Outputs of this process are as follows, with X being 0 or 1:

-   the availability flags availableFlagA₀, availableFlagA₁,     availableFlagB₀, availableFlagB₁ and availableFlagB₂ of the     neighbouring coding units, -   the reference indices refIdxLXA₀, refIdxLXA₁, refIdxLXB₀, refIdxLXB₁     and refIdxLXB₂ of the neighbouring coding units, -   the prediction list utilization flags predFlagLXA₀, predFlagLXA₁,     predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂ of the neighbouring     coding units, -   the motion vectors in 1/16 fractional-sample accuracy mvLXA₀,     mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂ of the neighbouring coding units, -   the bi-prediction weight indices gbiIdxA₀, gbiIdxA₁, gbiIdxB₀,     gbiIdxB₁, and gbiIdxB₂.

For the derivation of availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁ the following applies:

-   The luma location (xNbA₁, yNbA₁) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbHeight−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₁, yNbA₁) as inputs, and the output is assigned to the block     availability flag availableA₁. -   The variables availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁     are derived as follows:     -   If availableA₁ is equal to FALSE, availableFlagA₁ is set equal         to 0, both components of mvLXA₁ are set equal to 0, refIdxLXA₁         is set equal to −1 and predFlagLXA₁ is set equal to 0, with X         being 0 or 1, and gbiIdxA₁ is set equal to 0.     -   Otherwise, availableFlagA₁ is set equal to 1 and the following         assignments are made:

mvLXA ₁ 32 MvLX[xNbA₁][yNbA ₁]  (8-294)

refIdxLXA ₁=RefIdxLX[xNbA ₁][yNbA ₁]  (8-295)

predFlagLXA ₁=PredFlagLX[xNbA ₁][yNbA ₁]  (8-296)

gbiIdxA ₁ =GbiIdx[xNbA ₁][yNbA ₁]  (8-297)

For the derivation of availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁ the following applies:

-   The luma location (xNbB₁, yNbB₁) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth−1, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₁, yNbB₁) as inputs, and the output is assigned to the block     availability flag availableB₁. -   The variables availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₁ is set equal to 0, both components of mvLXB₁ are         set equal to 0, refIdxLXB₁ is set equal to −1 and predFlagLXB₁         is set equal to 0, with X being 0 or 1, and gbiIdxB₁ is set         equal to 0:         -   availableB₁ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₁, yNbB₁) have the same motion vectors and             the same reference indices.     -   Otherwise, availableFlagB₁ is set equal to 1 and the following         assignments are made:

mvLXB ₁=MvLX[xNbB ₁][yNbB ₁]  (8-298)

refIdxLXB ₁=RefIdxLX[xNbB ₁][yNbB ₁]  (8-299)

predFlagLXB ₁=PredFlagLX[xNbB ₁][yNbB ₁]  (8-300)

gbiIdxB ₁ =GbiIdx[xNbB ₁][yNbB ₁]  (8-301)

For the derivation of availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀ the following applies:

-   The luma location (xNbB₀, yNbB₀) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₀, yNbB₀) as inputs, and the output is assigned to the block     availability flag availableB₀. -   The variables availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₀ is set equal to 0, both components of mvLXB₀ are         set equal to 0, refIdxLXB₀ is set equal to −1 and predFlagLXB₀         is set equal to 0, with X being 0 or 1, and gbiIdxB₀ is set         equal to 0:         -   availableB₀ is equal to FALSE.         -   availableB₁ is equal to TRUE and the luma locations (xNbB₁,             yNbB₁) and(xNbB₀, yNbB₀) have the same motion vectors and             the same reference indices.         -   availableA₁ is equal to TRUE, the luma locations (xNbA₁,             yNbA₁) and (xNbB₀, yNbB₀) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.     -   Otherwise, availableFlagB₀ is set equal to 1 and the following         assignments are made:

mvLXB ₀=MvLX[xNbB ₀][yNbB ₀]  (8-302)

refIdxLXB ₀=RefIdxLX[xNbB ₀][yNbB ₀]  (8-303)

predFlagLXB ₀=PredFlagLX[xNbB ₀][yNbB ₀]  (8-304)

gbiIdxB ₀ =GbiIdx[xNbB ₀][yNbB ₀]  (8-305)

For the derivation of availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀ the following applies:

-   The luma location (xNbA₀, yNbA₀) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbWidth). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₀, yNbA₀) as inputs, and the output is assigned to the block     availability flag availableA₀. -   The variables availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagA₀ is set equal to 0, both components of mvLXA₀ are         set equal to 0, refIdxLXA₀ is set equal to −1 and predFlagLXA₀         is set equal to 0, with X being 0 or 1, and gbiIdxA₀ is set         equal to 0:         -   availableA₀ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE, the luma locations (xNbB₁,             yNbB₁) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbA₀, yNbA₀) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.     -   Otherwise, availableFlagA₀ is set equal to 1 and the following         assignments are made:

mvLXA ₀=MvLX[xNbA ₀][yNbA ₀]  (8-306)

refIdxLXA ₀=RefIdxLX[xNbA ₀][yNbA ₀]  (8-307)

predFlagLXA ₀=PredFlagLX[xNbA ₀][yNbA ₀]  (8-308)

gbiIdxA ₀ =GbiIdx[xNbA ₀][yNbA ₀]  (8-309)

For the derivation of availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂ the following applies:

-   The luma location (xNbB₂, yNbB₂) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₂, yNbB₂) as inputs, and the output is assigned to the block     availability flag availableB₂. -   The variables availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₂ is set equal to 0, both components of mvLXB₂ are         set equal to 0, refIdxLXB₂ is set equal to −1 and predFlagLXB₂         is set equal to 0, with X being 0 or 1, and gbiIdxB₂ is set         equal to 0:         -   availableB₂ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE and the luma locations (xNbB₁,             yNbB₁) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.         -   availableA₀ is equal to TRUE, the luma locations (xNbA₀,             yNbA₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge triangle flag[xCb][yCb]             is equal to 1.         -   availableFlagA₀+availableFlagA₁+availableFlagB₀+availableFlagB₁             is equal to 4 and merge_triangle_flag[xCb][yCb] is equal to             0.     -   Otherwise, availableFlagB₂ is set equal to 1 and the following         assignments are made:

mvLXB ₂=MvLX[xNbB ₂][yNbB ₂]  (8-310)

refIdxLXB ₂=RefIdxLX[xNbB ₂][yNbB ₂]  (8-311)

predFlagLXB ₂=PredFlagLX[xNbB ₂][yNbB ₂]  (8-312)

gbiIdxB ₂ =GbiIdx[xNbB ₂][yNbB ₂]  (8-313)

5.3 Embodiment #3

This embodiment is to align the conditions for invoking the checking of B2.

8.5.2.3 Derivation Process for Spatial Merging Candidates

Inputs to this process are:

-   a luma location (xCb, yCb) of the top-left sample of the current     luma coding block relative to the top-left luma sample of the     current picture, -   a variable cbWidth specifying the width of the current coding block     in luma samples, -   a variable cbHeight specifying the height of the current coding     block in luma samples.

Outputs of this process are as follows, with X being 0 or 1:

-   the availability flags availableFlagA₀, availableFlagA₁,     availableFlagB₀, availableFlagB₁ and availableFlagB₂ of the     neighbouring coding units, -   the reference indices refIdxLXA₀, refIdxLXA₁, refIdxLXB₀, refIdxLXB₁     and refIdxLXB₂ of the neighbouring coding units, -   the prediction list utilization flags predFlagLXA₀, predFlagLXA₁,     predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂ of the neighbouring     coding units, -   the motion vectors in 1/16 fractional-sample accuracy mvLXA₀,     mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂ of the neighbouring coding units, -   the bi-prediction weight indices gbiIdxA₀, gbiIdxA₁, gbiIdxB₀,     gbiIdxB₁, and gbiIdxB₂.

For the derivation of availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁ the following applies:

-   The luma location (xNbA₁, yNbA₁) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbHeight−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₁, yNbA₁) as inputs, and the output is assigned to the block     availability flag availableA₁. -   The variables availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁     are derived as follows:

For the derivation of availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁ the following applies:

-   The luma location (xNbB₁, yNbB₁) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth−1, yCb−1).

For the derivation of availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀ the following applies:

-   The luma location (xNbB₀, yNbB₀) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth, yCb−1).

For the derivation of availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀ the following applies:

-   The luma location (xNbA₀, yNbA₀) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbWidth).

For the derivation of availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂ the following applies:

-   The luma location (xNbB₂, yNbB₂) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₂, yNbB₂) as inputs, and the output is assigned to the block     availability flag availableB₂. -   The variables availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₂ is set equal to 0, both components of mvLXB₂ are         set equal to 0, refIdxLXB₂ is set equal to −1 and predFlagLXB₂         is set equal to 0, with X being 0 or 1, and gbiIdxB₂ is set         equal to 0:         -   availableB₂ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE and the lumalocations(xNbB₁,             yNbB₁) and(xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.         -   availableA₀ is equal to TRUE, the luma locations (xNbA₀,             yNbA₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.         -   availableFlagA₀+availableFlagA₁+availableFlagB₀+availableFlagB₁             is equal to 4 and merge triangle flag[xCb][yCb] is equal to             0.     -   Otherwise, availableFlagB₂ is set equal to 1 and the following         assignments are made:

mvLXB ₂=MvLX[xNbB ₂][yNbB ₂]  (8-310)

refIdxLXB ₂=RefIdxLX[xNbB ₂][yNbB ₂]  (8-311)

predFlagLXB ₂=PredFlagLX[xNbB ₂][yNbB ₂]  (8-312)

gbiIdxB ₂ =GbiIdx[xNbB ₂][yNbB ₂]  (8-313)

5.4 Embodiment #4

This embodiment is to align the conditions for invoking the checking of B2.

8.5.2.3 Derivation Process for Spatial Merging Candidates

Inputs to this process are:

-   a luma location (xCb, yCb) of the top-left sample of the current     luma coding block relative to the top-left luma sample of the     current picture, -   a variable cbWidth specifying the width of the current coding block     in luma samples, -   a variable cbHeight specifying the height of the current coding     block in luma samples.

Outputs of this process are as follows, with X being 0 or 1:

-   the availability flags availableFlagA₀, availableFlagA₁,     availableFlagB₀, availableFlagB₁ and availableFlagB₂ of the     neighbouring coding units, -   the reference indices refIdxLXA₀, refIdxLXA₁, refIdxLXB₀, refIdxLXB₁     and refIdxLXB₂ of the neighbouring coding units, -   the prediction list utilization flags predFlagLXA₀, predFlagLXA₁,     predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂ of the neighbouring     coding units, -   the motion vectors in 1/16 fractional-sample accuracy mvLXA₀,     mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂ of the neighbouring coding units, -   the bi-prediction weight indices gbiIdxA₀, gbiIdxA₁, gbiIdxB₀,     gbiIdxB₁, and gbiIdxB₂.

For the derivation of availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁ the following applies:

-   The luma location (xNbA₁, yNbA₁) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbHeight−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbA₁, yNbA₁) as inputs, and the output is assigned to the block     availability flag availableA₁. -   The variables availableFlagA₁, refIdxLXA₁, predFlagLXA₁ and mvLXA₁     are derived as follows:

For the derivation of availableFlagB₁, refIdxLXB₁, predFlagLXB₁ and mvLXB₁ the following applies:

-   The luma location (xNbB₁, yNbB₁) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth−1, yCb−1).

For the derivation of availableFlagB₀, refIdxLXB₀, predFlagLXB₀ and mvLXB₀ the following applies:

-   The luma location (xNbB₀, yNbB₀) inside the neighbouring luma coding     block is set equal to (xCb+cbWidth, yCb−1).

For the derivation of availableFlagA₀, refIdxLXA₀, predFlagLXA₀ and mvLXA₀ the following applies:

-   The luma location (xNbA₀, yNbA₀) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb+cbWidth).

For the derivation of availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂ the following applies:

-   The luma location (xNbB₂, yNbB₂) inside the neighbouring luma coding     block is set equal to (xCb−1, yCb−1). -   The availability derivation process for a block as specified in     clause 6.4.X [Ed. (BB): Neighbouring blocks availability checking     process tbd] is invoked with the current luma location (xCurr,     yCurr) set equal to (xCb, yCb) and the neighbouring luma location     (xNbB₂, yNbB₂) as inputs, and the output is assigned to the block     availability flag availableB₂. -   The variables availableFlagB₂, refIdxLXB₂, predFlagLXB₂ and mvLXB₂     are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₂ is set equal to 0, both components of mvLXB₂ are         set equal to 0, refIdxLXB₂ is set equal to −1 and predFlagLXB₂         is set equal to 0, with X being 0 or 1, and gbiIdxB₂ is set         equal to 0:         -   availableB₂ is equal to FALSE.         -   availableA₁ is equal to TRUE and the luma locations (xNbA₁,             yNbA₁) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₁ is equal to TRUE and the lumalocations(xNbB₁,             yNbB₁) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices.         -   availableB₀ is equal to TRUE, the luma locations (xNbB₀,             yNbB₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.         -   availableA₀ is equal to TRUE, the luma locations (xNbA₀,             yNbA₀) and (xNbB₂, yNbB₂) have the same motion vectors and             the same reference indices and merge_triangle_flag[xCb][yCb]             is equal to 1.         -   availableFlagA₀+availableFlagA₁+availableFlagB₀+availableFlagB₁             is equal to 4 and merge triangle flag[xCb][yCb] is equal to             0.     -   Otherwise, availableFlagB₂ is set equal to 1 and the following         assignments are made:

mvLXB ₂=MvLX[xNbB ₂][yNbB ₂]  (8-310)

refIdxLXB ₂=RefIdxLX[xNbB ₂][yNbB ₂]  (8-311)

predFlagLXB ₂=PredFlagLX[xNbB ₂][yNbB ₂]  (8-312)

gbiIdxB ₂ =GbiIdx[xNbB ₂][yNbB ₂]  (8-313)

5.5 Embodiment #5

This embodiment is to simplify the decision of initialized MV in ATMVP process.

8.5.5.4 Derivation Process for Subblock-Based Temporal Merging Base Motion Data

Inputs to this process are:

-   the location (xCtb, yCtb) of the top-left sample of the luma coding     tree block that contains the current coding block, -   the location (xColCtrCb, yColCtrCb) of the top-left sample of the     collocated luma coding block that covers the below-right center     sample. -   the availability flag availableFlagA₁ of the neighbouring coding     unit, -   the reference index refIdxLXA₁ of the neighbouring coding unit, -   the prediction list utilization flag predFlagLXA₁ of the     neighbouring coding unit, -   the motion vector in 1/16 fractional-sample accuracy mvLXA₁ of the     neighbouring coding unit.

Outputs of this process are:

-   the motion vectors ctrMvL0 and ctrMvL1, -   the prediction list utilization flags ctrPredFlagL0 and     ctrPredFlagL1, -   the temporal motion vector tempMv.

The variable tempMv is set as follows:

tempMv[0]=0  (8-529)

tempMv[1]=0   (8-530)

The variable currPic specifies the current picture.

When availableFlagA₁ is equal to TRUE, the following applies:

-   SET A VARIABLE X TO COLLOCATED_FROM_L0_FLAG. -   IF PREDFLAGLXA1 IS EQUAL TO 1 AND DIFFPICORDERCNT(COLPIC,     REFPICLIST[X][REFIDXLXA1]) IS EQUAL TO 0 ARE TRUE, TEMPMV IS SET     EQUAL TO MVLXA1. -   If all of the following conditions are true, tempMv is set equal to     mvL1A₁:     -   predFlagL1A₁ is equal to 1,     -   DiffPicOrderCnt(ColPic, RefPicList[1][refIdxL1A₁]) is equal to         0,     -   DiffPicOrderCnt(aPic, currPic) is less than or equal to 0 for         every picture aPic in every reference picture list of the         current slice,     -   slice type is equal to B,     -   collocated from l0 flag is equal to 0. -   Otherwise if all of the following conditions are true, tempMv is set     equal to mvL0A₁:     -   predFlagL0A₁ is equal to 1,     -   DiffPicOrderCnt(ColPic, RefPicList[0][refIdxL0A₁]) is equal to         0.

The location (xColCb, yColCb) of the collocated block inside ColPic is derived as follows.

xColCb=Clip3(xCtb, Min(CurPicWidthInSamplesY−1, xCtb+(1<<Ctb Log 2SizeY)+3), xColCtrCb+(tempMv[0]>>4))  (8-531)

yColCb=Clip3(yCtb, Min(CurPicHeightInSamplesY−1, yCtb+(1<<Ctb Log 2SizeY)−1), yColCtrCb+(tempMv[1]>>4))  (8-532)

The array colPredMode is set equal to the prediction mode array CuPredMode of the collocated picture specified by ColPic.

The motion vectors ctrMvL0 and ctrMvL1, and the prediction list utilization flags ctrPredFlagL0 and ctrPredFlagL1 are derived as follows:

5.6 Embodiment #6

Examples for alignment of derivation process of collocated MVs for sub-block and non-sub-block based methods.

8.5.2.12 Derivation Process for Collocated Motion Vectors

Inputs to this process are:

-   a variable currCb specifying the current coding block, -   a variable colCb specifying the collocated coding block inside the     collocated picture specified by ColPic, -   a luma location (xColCb, yColCb) specifying the top-left sample of     the collocated luma coding block specified by colCb relative to the     top-left luma sample of the collocated picture specified by ColPic, -   a reference index refIdxLX, with X being 0 or 1, -   a flag indicating a subblock temporal merging candidate sbFlag.

Outputs of this process are:

-   the motion vector prediction mvLXCol in 1/16 fractional-sample     accuracy, -   the availability flag availableFlagLXCol.

The variable currPic specifies the current picture.

The arrays predFlagL0Col[x] [y], mvL0Col[x] [y] and refIdxL0Col[x][y] are set equal to PredFlagL0[x][y], MvDmvrL0[x][y] and RefIdxL0[x][y], respectively, of the collocated picture specified by ColPic, and the arrays predFlagL1Col[x][y], mvL1Col[x][y] and refIdxL1Col[x][y] are set equal to PredFlagL1[x][y], MvDmvrL1[x][y] and RefIdxL1[x][y], respectively, of the collocated picture specified by ColPic.

The variables mvLXCol and availableFlagLXCol are derived as follows:

-   If colCb is coded in an intra or IBC prediction mode, both     components of mvLXCol are set equal to 0 and availableFlagLXCol is     set equal to 0. -   Otherwise, the motion vector mvCol, the reference index refIdxCol     and the reference list identifier listCol are derived as follows:     -   If sbFlag is equal to 0, availableFlagLXCol is set to 1 and the         following applies:         -   If predFlagL0Col[xColCb][yColCb] is equal to 0, mvCol,             refIdxCol and listCol are set equal to             mvL1Col[xColCb][yColCb], refIdxL1Col[xColCb][yColCb] and L1,             respectively.         -   Otherwise, if predFlagL0Col[xColCb][yColCb] is equal to 1             and predFlagL1Col[xColCb][yColCb] is equal to 0, mvCol,             refIdxCol and listCol are set equal to             mvL0Col[xColCb][yColCb], refIdxL0Col[xColCb][yColCb] and L0,             respectively.         -   Otherwise (predFlagL0Col[xColCb][yColCb] is equal to 1 and             predFlagl1Col[xColCb][yColCb] is equal to 1), the following             assignments are made:             -   If NoBackwardPredFlag is equal to 1, mvCol, refIdxCol                 and listCol are set equal to mvLXCol[xColCb][yColCb],                 refIdxLXCol[xColCb][yColCb] and LX, respectively.             -   Otherwise, mvCol, refIdxCol and listCol are set equal to                 mvLNCol[xColCb][yColCb], refIdxLNCol[xColCb][yColCb] and                 LN, respectively, with N being the value of                 collocated_from_l0_flag.     -   Otherwise (sbFlag is equal to 1), the following applies:         -   If PredFlagLXCol[xColCb][yColCb] is equal to 1, mvCol,             refIdxCol, and listCol are set equal to             mvLXCol[xColCb][yColCb], refIdxLXCol[xColCb][yColCb], and             LX, respectively, availableFlagLXCol is set to 1.         -   Otherwise (PredFlagLXCol[xColCb][yColCb] is equal to 0), the             following applies:             -   IfDiffPicOrderCnt(aPic, currPic) is less than or equal                 to 0 for every picture aPic in every reference picture                 list of the current slice and                 PredFlagLYCol[xColCb][yColCb] is equal to 1, mvCol,                 refIdxCol, and listCol are set to                 mvLyCol[xColCb][yColCb], refIdxLYCol[xColCb][yColCb] and                 LY, respectively, with Y being equal to !X where X being                 the value of X this process is invoked for.                 AvailableFlagLXCol is set to 1.             -   Both the components of mvLXCol are set to 0 and                 availableFlagLXCol is set equal to 0.         -   When availableFlagLXCol is equal to TRUE, mvLXCol and             availableFlagLXCol are derived as follows:             -   If LongTermRefPic(currPic, currCb, refIdxLX, LX) is not                 equal to LongTermRefPic(ColPic, colCb, refIdxCol,                 listCol), both components of mvLXCol are set equal to 0                 and availableFlagLXCol is set equal to 0.             -   Otherwise, the variable availableFlagLXCol is set equal                 to 1, refPicList[listCol][refIdxCol] is set to be the                 picture with reference index refIdxCol in the reference                 picture list listCol of the slice containing coding                 block colCb in the collocated picture specified by                 ColPic, and the following applies:

FIG. 22 is a block diagram of a video processing apparatus 2200. The apparatus 2200 may be used to implement one or more of the methods described herein. The apparatus 2200 may be embodied in a smartphone, tablet, computer, Internet of Things (IoT) receiver, and so on. The apparatus 2200 may include one or more processors 2202, one or more memories 2204 and video processing hardware 2206. The processor(s) 2202 may be configured to implement one or more methods described in the present document. The memory (memories) 2204 may be used for storing data and code used for implementing the methods and techniques described herein. The video processing hardware 2206 may be used to implement, in hardware circuitry, some techniques described in the present document. The video processing hardware 2206 may be partially or completely includes within the processor(s) 2202 in the form of dedicated hardware, or graphical processor unit (GPU) or specialized signal processing blocks.

Some embodiments may be described using the following clause-based description.

Some example embodiments of techniques described in item 1 of section 4 include:

1. A method of video processing (e. g., method 2300 depicted in FIG. 23), comprising applying (2302) a pruning process to a merge list construction of a current video block that is partitioned using a triangular partition mode (TMP) in which the current video block is partitioned into at least two non-rectangular sub-blocks, wherein the pruning process is same as another pruning process for another video block that is partitioned using a non-TMP partition; and performing (2304) a conversion between the current video block and a bitstream representation of the current video block based on the merge list construction.

2. The method of claim 1, wherein the pruning process comprises using a partial pruning to spatial merge candidates of the current video block.

3. The method of claim 1, wherein the pruning process comprises applying full or partial pruning to the current video block based on a block dimension rule that specifies to use full or partial pruning based on dimensions of the current video block.

4. The method of claim 1, wherein the pruning process comprises using a different order of neighboring blocks during the merge list construction process.

Some example embodiments of techniques described in item 2 of section 4 include:

1. A method of video processing, comprising: determining, during a conversion between a current video block and a bitstream representation of the current video block, about availability of an alternative temporal motion vector predictor coding (ATMVP) mode for the conversion based on list X of a neighboring block of the current video block, wherein Xis an integer and a value of X depends on an encoding condition of the current video block, and performing the conversion based on the availability of the ATMVP mode.

2. The method of claim 1, wherein X indicates a location of a collocated video picture from which a temporal motion vector prediction used for the conversion between the current video block and the bitstream representation is performed.

3. The method of claim 1, wherein X is determined by comparing picture order counts (POCs) of all reference pictures in all reference lists for the current video block with a POC of a current video picture of the current video block.

4. The method of claim 3, wherein in case that the comparing shows that the POCs are <=the POC of the current picture, then setting X=1, otherwise, setting X=0.

5. The method of claim 1, wherein motion information stored in a history-based motion vector predictor table is used for initializing motion vector in the ATMVP mode.

Some example embodiments of techniques described in item 3 of section 4 include:

1. A method of video processing, comprising: determining, during a conversion between a current video block and a bitstream representation of the current video block, that a sub-block based coding technique in which the current video block is partitioned into at least two sub-blocks, wherein each sub-block capable of deriving its own motion information, is used for the conversion; and performing the conversion using a merge list construction process for the current video block that is aligned with a block based derivation process for collocated motion vectors.

2. The method of claim 1, wherein the merge list construction process and the derivation process comprise performing uni-prediction from list Y, and wherein motion vectors of list Y are scaled to a target reference picture list X.

3. The method of claim 1, wherein the merge list construction process and the derivation process comprise performing bi-prediction with target reference picture list X, then motion vectors of list Y are scaled to that of list X, where Y is determined according to a rule.

Some example embodiments of techniques described in item 4 of section 4 include:

1. A method of video processing, comprising: determining, based on dimensions of a current video block of a video picture and/or an enablement of a merge sharing status in which merge candidates from different coding tools are shared, between a condition being met and the condition being not met; and performing a conversion between the current video block and a bitstream representation of the current video block based on the condition.

2. The method of claim 1, wherein the performing the conversion comprises skipping deriving spatial merge candidates in case that the condition is met.

3. The method of claim 1, wherein the performing the conversion comprises skipping deriving history-based motion vector candidates in case that the condition is met.

4. The method of any of claims 1-3, wherein it is determined that the condition is met based on the current video block being under a shared node in the video picture.

Some example embodiments of techniques described in item 5 of section 4 include:

1. A method of video processing, comprising: making a determination, during a conversion between a current video block and a bitstream representation of the current video block, that a coding tool is disabled for the conversion, wherein the bitstream representation is configured to provide an indication that a maximum number of merge candidates for the coding tool is zero; and performing the conversion using the determination that the coding tool is disabled.

2. The method of claim 1, wherein the coding tool corresponds to intra block copy in which pixels of the current video block are coded from other pixels in a video region of the current video block.

3. The method of claim 1, wherein the coding tool is a sub-block coding tool.

4. The method of claim 3, wherein the sub-block coding tool is an affine coding tool or an alternate motion vector predictor tool.

5. The method of any of claims 1-4, wherein the performing the conversion includes processing the bitstream by skipping syntax elements related to the coding tool.

Some example embodiments of techniques described in item 6 of section 4 include:

1. A method of video processing, comprising: making a determination, during a conversion between a current video block and a bitstream representation of the current video block using a rule that specifies that a first syntax element in the bitstream representation is conditionally present based on a second syntax element indicative of a maximum number of merge candidates used by a coding tool used during the conversion; and performing the conversion between the current video block and a bitstream representation of the current video block based on the determination.

2. The method of claim 1, wherein the first syntax element corresponds to a merge flag.

3. The method of claim 1, wherein the first syntax element corresponds to a skip flag.

4. The method of any of claims 1-3, wherein the coding tool is a sub-band coding tool and the second syntax element corresponds to a maximum allowed merge candidates for the sub-band coding tool.

34. The method of any of clauses 1 to 33, wherein the conversion includes generating the bitstream representation from the current video block.

35. The method of any of clauses 1 to 33, wherein the conversion includes generating samples of the current video block from the bitstream representation.

36. A video processing apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1 to 35.

37. A computer readable medium having code stored thereon, the code, upon execution, causing a processor to implement a method recited in any one or more of clauses 1 to 35.

FIG. 24 is a block diagram showing an example video processing system 2400 in which various techniques disclosed herein may be implemented. Various implementations may include some or all of the components of the system 2400. The system 2400 may include input 2402 for receiving video content. The video content may be received in a raw or uncompressed format, e.g., 8 or 10 bit multi-component pixel values, or may be in a compressed or encoded format. The input 2402 may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interface include wired interfaces such as Ethernet, passive optical network (PON), etc. and wireless interfaces such as Wi-Fi or cellular interfaces.

The system 2400 may include a coding component 2404 that may implement the various coding or encoding methods described in the present document. The coding component 2404 may reduce the average bitrate of video from the input 2402 to the output of the coding component 2404 to produce a coded representation of the video. The coding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the coding component 2404 may be either stored, or transmitted via a communication connected, as represented by the component 2406. The stored or communicated bitstream (or coded) representation of the video received at the input 2402 may be wed by the component 2408 for generating pixel values or displayable video that is sent to a display interface 2410. The process of generating user-viewable video from the bitstream representation is sometimes called video decompression. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be appreciated that the coding tools or operations are used at an encoder and corresponding decoding tools or operations that reverse the results of the coding will be performed by a decoder.

Examples of a peripheral bus interface or a display interface may include universal serial bus (USB) or high definition multimedia interface (HDMI) or Displayport, and so on. Examples of storage interfaces include SATA (serial advanced technology attachment), PCI, IDE interface, and the like. The techniques described in the present document may be embodied in various electronic devices such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and/or video display.

FIG. 25 is a flowchart for an example of a visual media processing method. Steps of this flowchart are discussed in connection with example 5d in Section 4 of this document. At step 2502, the process performs a conversion between a current video block of a visual media data and a bitstream representation of the current video block, wherein the bitstream representation is configured according to a format rule that specifies that a syntax element is selectively included or excluded in the bitstream representation indicative of a maximum number of merge candidates for a coding tool, thereby indicating whether the coding tool is enabled or disabled for the conversion, wherein the maximum number of merge candidates for the coding tool is zero or a positive number.

FIG. 26 is a flowchart for an example of a visual media processing method. Steps of this flowchart are discussed in connection with example 13 in Section 4 of this document. At step 2602, the process performs a conversion between a video comprising one or more video regions comprising multiple video blocks and a bitstream representation of the video, wherein the bitstream representation conforms to a format rule specifying that a number of allowed geometric partitioning mode (GPM) motion candidates for a video region determines whether a syntax element related to applicability of a coding tool to the video region is included in the bitstream representation, wherein the coding tool is different from a GPM coding tool, wherein the GPM comprises splitting a video block into multiple prediction partitions to apply motion prediction separately, and at least one partition having a non-rectangular shape.

FIG. 27 is a flowchart for an example of a visual media processing method. Steps of this flowchart are discussed in connection with example 14 in Section 4 of this document. At step 2702, the process performs a conversion between a current video unit of a visual media data and a bitstream representation of the visual media data, wherein the bitstream representation is configured in accordance with a format rule that specifies that a maximum transform block size is equal to or less than a maximum coding tree unit (CTU) size used for the conversion.

FIG. 28 is a flowchart for an example of a visual media processing method. Steps of this flowchart are discussed in connection with example 15 in Section 4 of this document. At step 2802, the process performs a conversion between a current video block of a visual media data and a bitstream representation of the current video block, wherein the conversion uses an adaptive loop filter (ALF) in which coefficients of the ALF filter are based on a depth of a sample in a video region of the current video block.

FIG. 29 is a flowchart for an example of a visual media processing method. Steps of this flowchart are discussed in connection with example 16 in Section 4 of this document. At step 2902, the process performs a conversion between a current video block of a visual media data and a bitstream representation of the current video block using an adaptive loop filter (ALF), wherein the bitstream representation is configured according to a format rule specifying that one or more syntax elements included in the bitstream representation indicative of whether an ALF filter applied to the current video block is determined based on an adaptation parameter set (APS) or based on fixed filter sets.

Some embodiments of the present document are presented in clause-based format.

A1. A method of visual media processing, comprising:

performing a conversion between a current video block of a visual media data and a bitstream representation of the current video block, wherein the bitstream representation is configured according to a format rule that specifies that a syntax element is selectively included or excluded in the bitstream representation indicative of a maximum number of merge candidates for a coding tool, thereby indicating whether the coding tool is enabled or disabled for the conversion,

wherein the maximum number of merge candidates for the coding tool is zero or a positive number.

A2. The method of clause A1, wherein the format rule specifies that the syntax element is excluded in the bitstream representation in response to determining that the coding tool is disabled for the conversion.

A3. The method of clause A2, wherein in a case that the maximum number of merge candidates for the coding tool is zero, the format rule specifies excluding the syntax element in the bitstream representation.

A4. The method of clause A3, wherein the coding tool corresponds to intra block cow in which pixels of the current video block are coded from other pixels in a video region of the current video block.

A5. The method of any one or more of clauses A1-A4, wherein the coding tool corresponds to a regular merge, Mmerge with motion vector differences (MMVD), combined intra-inter prediction (CIIP), triangular partition mode (TPM), decoder side motion vector refinement (DMVR).

A6. The method of any one or more of clause A1-A4, wherein the coding tool is a sub-block coding tool.

A7. The method of clause A6, wherein the sub-block coding tool is an affine coding tool or an alternate motion vector predictor tool.

A8. The method of any one or more of clauses A1-A4, wherein the performing the conversion includes processing the bitstream by skipping syntax elements related to the coding tool.

A9. The method of any one or more of clauses A1-A4, wherein the performing the conversion includes processing the bitstream to determine that the maximum number of merge candidates for the coding tool is unequal to zero.

A10. The method of any one or more of clauses A1-A9, wherein the conversion includes determining that the maximum number of merge candidates for the coding tool is unequal to zero.

E1. A method of visual media processing, comprising:

performing a conversion between a video comprising one or more video regions comprising multiple video blocks and a bitstream representation of the video,

wherein the bitstream representation conforms to a format rule specifying that a number of allowed geometric partitioning mode (GPM) motion candidates for a video region determines whether a syntax element related to applicability of a coding tool to the video region is included in the bitstream representation, wherein the coding tool is different from a GPM coding tool, wherein the GPM comprises splitting a video block into multiple prediction partitions to apply motion prediction separately, and at least one partition having a non-rectangular shape.

E2. The method of clause E1, wherein the coding tool corresponds to a combined inter-intra prediction (CIIP) mode, and wherein in a case that the number of allowed GPM motion candidates exceeds the threshold value, the format rule specifies including the one or more syntax elements in the bitstream representation.

E3. The method of any one or more of clauses E1-E2, wherein the threshold value equals one.

E4. The method of any one or more of clauses E1-E3, wherein in a case that the number of allowed GPM motion candidates is less than or equal to the threshold value, the format rule specifies excluding the syntax element in the bitstream representation.

B1. A method of visual media processing, comprising:

performing a conversion between a current video unit of a visual media data and a bitstream representation of the visual media data, wherein the bitstream representation is configured in accordance with a format rule that specifies that a maximum transform block size is equal to or less than a maximum coding tree unit (CTU) size used for the conversion.

B2. The method of clause B1, wherein the format rule specifies selectively including a syntax element indicative of the maximum transform block size in the bitstream representation based on the maximum CTU size.

B3. The method of clause B2, wherein the format rule specifies excluding a syntax element indicative of the maximum transform block size in the bitstream representation based on a determination that the maximum CTU size is less than or equal to a defined M×N block size.

B4. The method of clause B3, wherein M=32 and N=32.

C1. A method of visual media processing, comprising:

performing a conversion between a current video block of a visual media data and a bitstream representation of the current video block, wherein the conversion uses an adaptive loop filter (ALF) in which coefficients of the ALF filter are based on a depth of a sample in a video region of the current video block.

C2. The method of clause C1, wherein the ALF filter coefficients correspond to chroma ALF filter coefficients.

C3. The method of clause C1, wherein the ALF filter coefficients correspond to luma ALF filter coefficients.

D1. A method of visual media processing, comprising:

performing a conversion between a current video block of a visual media data and a bitstream representation of the current video block using an adaptive loop filter (ALF), wherein the bitstream representation is configured according to a format rule specifying that one or more syntax elements included in the bitstream representation indicative of whether an ALF filter applied to the current video block is determined based on an adaptation parameter set (APS) or based on fixed filter sets.

D2. The method of clause D1, wherein in a case that a number of available ALF APSs is greater than zero, the format rule further specifies that the one or more syntax elements are included in the bitstream representation.

D3. The method of clause D1, wherein in a case that the ALF is based on the APS, the format rule further specifies that the one or more syntax elements are included in the bitstream representation indicative of an index of the APS.

D4. The method of clause D3, wherein the index of the APS is included in the bitstream representation using a coding technique.

D5. The method of clause D1, wherein the coding technique includes one of: Fixed-length coding, unary coding, truncated unary coding, truncated binary coding, or exp-golomb coding.

L1. The method of any one or more of clauses A1 to D5, wherein the conversion includes generating the bitstream representation from the current video block.

L2. The method of any one or more of clauses A1 to D5, wherein the conversion includes generating samples of the current video block from the bitstream representation.

L3. A video processing apparatus comprising a processor configured to implement a method recited in any one or more of clauses A1 to D5.

L4. A computer readable medium having code stored thereon, the code, upon execution, causing a processor to implement a method recited in any one or more of clauses A1 to D5.

In the present document, the term “video processing” or “visual media processing” may refer to video encoding, video decoding, video compression or video decompression. For example, video compression algorithms may be applied during conversion from pixel representation of a video to a corresponding bitstream representation or vice versa. The bitstream representation of a current video block may, for example, correspond to bits that are either co-located or spread in different places within the bitstream, as is defined by the syntax. For example, a macroblock may be encoded in terms of transformed and coded error residual values and also using bits in headers and other fields in the bitstream. Furthermore, during conversion, a decoder may parse a bitstream with the knowledge that some fields may be present, or absent, based on the determination, as is described in the above solutions. Similarly, an encoder may determine that certain syntax fields are or are not to be included and generate the coded representation accordingly by including or excluding the syntax fields from the coded representation. It will be appreciated that the disclosed techniques may be embodied in video encoders or decoders to improve compression efficiency using techniques that include the use of sub-block based motion vector refinement.

From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the presently disclosed technology is not limited except as by the appended claims.

The disclosed and other solutions, examples, embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

While this patent document contains many specifics, these should not be construed as limitations on the scope of any subject matter or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular techniques. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document. 

What is claimed is:
 1. A method of processing video data, comprising: performing a conversion between a video comprising one or more coding tree units and a bitstream of the video, wherein the bitstream is configured in accordance with a format rule, wherein the format rule specifies that only when a size of the coding tree unit of the video is greater than a defined M×N size, a first syntax element indicative of a maximum transform block size is included in the bitstream, where M and N are integers.
 2. The method of claim 1, wherein M=32 and N=32.
 3. The method of claim 1, wherein the format rule further specifies that the maximum transform block size is equal to or less than the size of the coding tree unit.
 4. The method of claim 2, further comprising: determining that an adaptive loop filter (ALF) process is applied for a current coding tree block of one or more coding tree blocks in a video region, wherein the bitstream is configured according to the format rule specifying that a single one second syntax element which indicates whether an ALF filter applied to the current coding tree block is based on an adaptation parameter set (APS) or based on fixed filter sets is conditionally included in the bitstream.
 5. The method of claim 4, wherein in case that the ALF filter is based on the APS, the format rule further specifies that a third syntax element is conditionally included in the bitstream, which is used to derive an index of the APS that includes the ALF filter applied to the current coding tree block.
 6. The method of claim 5, wherein the third syntax element is coded with a truncated binary coding technique.
 7. The method of claim 5, wherein the third syntax element is indicative of a sequence which the APS that includes the ALF filter applied to the current coding tree block belongs in available ALF APSs of the video region.
 8. The method of claim 4, wherein in a case that a number of available ALF AP S s of the video region is greater than zero, the format rule further specifies that the second syntax element is included in the bitstream.
 9. The method of claim 4, wherein in case that one of the fixed filter sets is applied to the current coding tree block, the format rule further specifies that a fourth syntax element is included in the bitstream, and a value of the fourth syntax element specifies an index of the one fixed filter that is applied to the current coding tree block.
 10. The method of claim 7, wherein the video region is a slice.
 11. The method of claim 1, wherein the conversion includes encoding the video into the bitstream.
 12. The method of claim 1, wherein the conversion includes decoding the video from the bitstream.
 13. An apparatus for processing video data comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to: perform a conversion between a video comprising one or more coding tree units and a bitstream of the video, wherein the bitstream is configured in accordance with a format rule, wherein the format rule specifies that only when a size of the coding tree unit of the video is greater than a defined M×N size, a first syntax element indicative of a maximum transform block size is included in the bitstream, where M and N are integers.
 14. The apparatus of claim 13, wherein M=32 and N=32; and wherein the format rule further specifies that the maximum transform block size is equal to or less than the size of the coding tree unit.
 15. The apparatus of claim 14, the instructions further cause the processor to: determine that an adaptive loop filter (ALF) process is applied for a current coding tree block of one or more coding tree blocks in a video region, wherein the bitstream is configured according to the format rule specifying that a single one second syntax element which indicates whether an ALF filter applied to the current coding tree block is based on an adaptation parameter set (APS) or based on fixed filter sets is conditionally included in the bitstream, wherein in case that the ALF filter is based on the APS, the format rule further specifies that a third syntax element is conditionally included in the bitstream, which is used to derive an index of the APS that includes the ALF filter applied to the current coding tree block; wherein the third syntax element is coded with a truncated binary coding technique; wherein the third syntax element is indicative of a sequence which the APS that includes the ALF filter applied to the current coding tree block belongs in available ALF APSs of the video region; wherein in a case that a number of available ALF APSs of the video region is greater than zero, the format rule further specifies that the second syntax element is included in the bitstream; wherein in case that one of the fixed filter sets is applied to the current coding tree block, the format rule further specifies that a fourth syntax element is included in the bitstream, and a value of the fourth syntax element specifies an index of the one fixed filter that is applied to the current coding tree block; and wherein the video region is a slice.
 16. A non-transitory computer-readable storage medium storing instructions that cause a processor to: perform a conversion between a video comprising one or more coding tree units and a bitstream of the video, wherein the bitstream is configured in accordance with a format rule, wherein the format rule specifies that only when a size of the coding tree unit of the video is greater than a defined M×N size, a first syntax element indicative of a maximum transform block size is included in the bitstream, where M and N are integers.
 17. The non-transitory computer-readable storage medium of claim 16, wherein M=32 and N=32; and wherein the format rule further specifies that the maximum transform block size is equal to or less than the size of the coding tree unit.
 18. The non-transitory computer-readable storage medium of claim 17, the processor is further caused to: determine that an adaptive loop filter (ALF) process is applied for a current coding tree block of one or more coding tree blocks in a video region, wherein the bitstream is configured according to the format rule specifying that a single one second syntax element which indicates whether an ALF filter applied to the current coding tree block is based on an adaptation parameter set (APS) or based on fixed filter sets is conditionally included in the bitstream, wherein in case that the ALF filter is based on the APS, the format rule further specifies that a third syntax element is conditionally included in the bitstream, which is used to derive an index of the APS that includes the ALF filter applied to the current coding tree block; wherein the third syntax element is coded with a truncated binary coding technique; wherein the third syntax element is indicative of a sequence which the APS that includes the ALF filter applied to the current coding tree block belongs in available ALF APSs of the video region; wherein in a case that a number of available ALF APSs of the video region is greater than zero, the format rule further specifies that the second syntax element is included in the bitstream; wherein in case that one of the fixed filter sets is applied to the current coding tree block, the format rule further specifies that a fourth syntax element is included in the bitstream, and a value of the fourth syntax element specifies an index of the one fixed filter that is applied to the current coding tree block; and wherein the video region is a slice.
 19. A non-transitory computer-readable recording medium storing a bitstream of a video which is generated by a method performed by a video processing apparatus, wherein the method comprises: generating a bitstream from a video comprising one or more coding tree units, wherein the bitstream is configured in accordance with a format rule, wherein the format rule specifies that only when a size of the coding tree unit of the video is greater than a defined M×N size, a first syntax element indicative of a maximum transform block size is included in the bitstream, where M and N are integers.
 20. The non-transitory computer-readable storage medium of claim 19, wherein M=32 and N=32; wherein the format rule further specifies that the maximum transform block size is equal to or less than the size of the coding tree unit; wherein the method further comprises: determining that an adaptive loop filter (ALF) process is applied for a current coding tree block of one or more coding tree blocks in a video region, wherein the bitstream is configured according to the format rule specifying that a single one second syntax element which indicates whether an ALF filter applied to the current coding tree block is based on an adaptation parameter set (APS) or based on fixed filter sets is conditionally included in the bitstream, wherein in case that the ALF filter is based on the APS, the format rule further specifies that a third syntax element is conditionally included in the bitstream, which is used to derive an index of the APS that includes the ALF filter applied to the current coding tree block; wherein the third syntax element is coded with a truncated binary coding technique; wherein the third syntax element is indicative of a sequence which the APS that includes the ALF filter applied to the current coding tree block belongs in available ALF APSs of the video region; wherein in a case that a number of available ALF APSs of the video region is greater than zero, the format rule further specifies that the second syntax element is included in the bitstream; wherein in case that one of the fixed filter sets is applied to the current coding tree block, the format rule further specifies that a fourth syntax element is included in the bitstream, and a value of the fourth syntax element specifies an index of the one fixed filter that is applied to the current coding tree block; and wherein the video region is a slice. 